It seems to me that MySQL and PostgreSQL are exhibitting some dubious guessing behaviour as to which column it refers to, or perhaps they are making some requirement of the order by to contain a column that is in the resultset ??? If name were only in test11 then what would MySQL and PostgreSQL do ?
-----Original Message----- From: Will Leshner [mailto:[EMAIL PROTECTED] Sent: 26 May 2005 15:18 To: Forum SQLite Subject: [sqlite] qualified names in WHERE clause I guess I never really noticed this before (since I only use SQLite, of course :) ). But consider a query like this: SELECT test2.* FROM test2,test11 WHERE test2.id=test11.id ORDER BY name If the 'name' column happens to be a column in both test2 and test11, then SQLite will return an error. You need to qualify 'name' with 'test2.' to make the query acceptable. Apparently MySQL and PostgreSQL are able to recognize that 'name' refers to the 'name' in the result set and are able to disambiguate it.
