I agree with Ramasubramaniam, that in the case of an aggregate function,
default alias should be the same as the expression, with the non-standard
ANSI characters removed. Just like this:

SELECT MAX(SELL_PRICE) FROM DB.INV_MASTER

should return MAXSELL_PRICE instead of EXPR(n) or SELL_PRICE as Joe Geiser
suggests (sorry Joe). Also, maybe an expression like 1/count(*) should
return a default column header prefixed with a underscore.

Also, I would vote for implicit column headers, that is making the AS word
optional. For example,

SELECT  result/100 AS Note FROM exams;

SELECT result/100 AS "This is my note" FROM exams;

SELECT result/100 "This is my note" FROM exams;

should be all valid.

Anyway, I'm so happy it'll be added to Allbase, I would accept almost any
syntax flavor (and compromise)!

Michel Gauthier
Donohue Inc.


Kumaran N S <[log in to unmask]> wrote in message
news:F4B1826B1A21D211AEC5006008207AF402114BB8@dogbert.csillc.com...
> Hello All,
>
> This is regarding the Allbase "AS Clause" Enhancement. The Database LAB
> is working on the AS Clause Enhancement.
>
> The objective of this enhancement is to allow the users to specify an
> alias name for a column or an expression in the Select List of the
> SELECT Statement and this alias name will be used as the column heading
> in the result. The column aliases cannot be referenced elsewhere in the
> query.
>
> The LAB is looking for inputs from you regarding the above stated
> requirements. Do you feel that the "AS Clause" should have any
> additional features? If yes, please mention the features that you are
> looking for and it's necessity. Your inputs will be very valuable for
> the LAB.
>
> --
> Thanks and regards,
> Kumaran
>