If you do a select and use the "AS 'alias'" for a table and also do a "JOIN USING <col list>", you get a sql error: no such column <tablename>.<col name>. So, if you have table User with fields a,b and table UserInfo with fields a,c, the following gives the error "User.a no such column":
SELECT U.b,I.c FROM User as U JOIN UserInfo as I USING a;
whereas, the following sql will work just fine:
SELECT User.b,UserInfo.c FROM User JOIN UserInfo USING a;
Of course, "SELECT U.b FROM User as U;" works just fine.
According to the docs on the website, this should be supported. If you have lots of fields to extract from multiple tables, this can get painful depending on the length of the table names you use.
I have submitted a bug report.
Michael Hunley
Senior Engineer
PocketPurchase, Inc.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
