You have raised some vaild concerns for sure. But, the rest of the known SQL database universe (Oracle, SQL Server, MySQL, Advantage, Access(?), and etc.) does it the other way round. The only reason I prefer the change is to allow for greater cross platform migration.
If there are those who obviously have a great deal invested in the current implementation, then something like a sticky PRAGMA would be a very good solution. This would allow the existing code base be protected, but future migration to be more "industry standard." In the old IBM days the "c.foo" would require a "gray area" in the manual:-)
If the main issue at hand is cross-database compatability, then there is a good method that already exists as defined by the SQL standards - "AS". If one were to use that for every returned column in the select list then you would have the same result using this on any SQL database. Moreover, using AS all the time allows a type of uniformity on selects that contain arbitrary expressions in the select list, which typically use AS anyway. And for people such as myself who are inclined to generate our SQL from a data dictionary, making it generate AS all the time is trivial. Those are some thoughts. -- Darren Duncan
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
