On Sep 15, 2014, at 4:48 PM, Richard Hipp <d...@sqlite.org> wrote: > On Sun, Sep 14, 2014 at 12:18 AM, Lea Verou <l...@verou.me> wrote: > >> Per the 3.7.11 changelog [1], queries of the form SELECT max(x), y FROM >> table return the value of y from the same row that contains the maximum x >> value. However, this: >> >> select y from (SELECT max(x), y FROM table); >> >> would not return the same y rows. This would work as expected: >> >> select m, y from (SELECT max(x) as m, y FROM table); >> > > I'm not sure if this qualifies as a "bug" or not, since the behavior is > unspecified in the official documentation. Nevertheless, it is now fixed > on trunk.
Considering that the original query is non-sensical to start with, not quite sure what’s there to fix in the first place. Aside, of course, from raising an exception. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
