Wouldn't implementation dependent mean it's not really standardized? The way I read it the query could still be considered legal in some dbms and not in others (which stinks).
Besides, the current version of SQLite seems to match on the first tables names which is consistent with expectations from other databases and not prohibited by the standard (in the way I read it) and backwards compatibility seems to be the most important thing here.. sqlite> create table t(a text, b text); sqlite> insert into t values('one', 'two'); sqlite> insert into t values('three', 'four'); sqlite> select a, b from t union select b,a from t; a b ---------- ---------- four three one two three four two one sqlite> select a, b from t union select b,a from t order by a,b; a b ---------- ---------- four three one two three four two one sqlite> select a, b from t union select b,a from t order by b,a; a b ---------- ---------- three four two one four three one two sqlite> So from this example seems like what we really need is to teach SQLite how to count... four, one, three, two.. sheesh. :-) Sam ------------------------------------------- We're Hiring! Seeking a passionate developer to join our team building products. Position is in the Washington D.C. metro area. If interested contact [EMAIL PROTECTED] -----Original Message----- From: Dennis Cote [mailto:[EMAIL PROTECTED] Sent: Thursday, April 12, 2007 6:05 PM To: [EMAIL PROTECTED] Subject: Re: [sqlite] Help with SQL syntax. Ticket #2296 ... Otherwise, the <column name> of the i-th column of TR is implementation dependent and not equivalent to the <column name> of any column, other than itself, of any table referenced by any <table reference> contained in the SQL statement. ... HTH Dennis Cote ---------------------------------------------------------------------------- - To unsubscribe, send email to [EMAIL PROTECTED] ---------------------------------------------------------------------------- - ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------