Hello!
Up to version 3.5.3, SQLite would happily execute this SQL without complaints:
drop table if exists t;
create table t (c);
select
(select count() from t t_inner
group by t_outer.c)
from t t_outer;
This behaviour changed in version 3.5.4. From then on, SQLite issues an "SQL
error near line 4: no such column: t_outer.c". This also shows in the most
recent version (3.6.14).
I searched both the change log and the timeline for 3.5.4 but could not find
any explicit mention of GROUP BY.
I did note, however, that http://www.sqlite.org/releaselog/3_5_4.html talks
about bringing "the processing of ORDER BY into compliance with the SQL
standard".
Questions:
* Does the ORDER BY change also apply to GROUP BY?
* Are there any test cases for the new behaviour?
I failed to find any in 3.6.14 test suite.
* Post 3.5.3, the query works fine if I GROUP BY the inner table:
select
(select count() from t t_inner
group by t_inner.c)
from t t_outer;
Is this the intended behaviour and should users update
their SQL accordingly?
Thanks for any answers,
Ralf
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
