Although the idea of having a default (valid SQL-92 & ODBC) column
name derived from functions, expressions, and constants may be nice,
I'm not sure if that is part of the SQL standard.  Even if it is, what is
being proposed will solve these problems with just a little extra typing

SELECT MAX(SELL_PRICE) AS MAXSELL_PRICE FROM DB.INV_MASTER

After waiting *SO LONG* for this enhancement, I'm extremely reluctant
to try adding adding to the original request.  Obviously if it turns out that
these can be added with little to no additional effort, then by all means.
If it means delaying the addition of the "AS" clause even by one Express
or PowerPatch (regardless of its spelling :) Release, then let's add these
suggestions in as separate Enhancement issues on the SIG Allbase
Ballot.

Regards,
Michael L Gueterman
Easy Does It Technologies
SIG Web Co-Chair
http://www.editcorp.com
voice: (888) 858-EDIT -or- (573) 368-5478
--

-----Original Message-----
From:   Michel Gauthier [SMTP:[log in to unmask]]
Sent:   Thursday, October 21, 1999 4:20 PM
To:     [log in to unmask]
Subject:        Re: [HP3000-L] ALLBASE "AS Clause" Enhancement - Your inputs required

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.
<snip>