On Fri, May 4, 2012 at 4:04 PM, Richard Hipp <d...@sqlite.org> wrote: > Correction: The one that it encounters first, since subsequent rows of the > same value will not trigger a new copy of values into the output registers, > since only a new min/max does that.
But surely that's non-deterministic, or you'd like users to think so. I think that leaves SQLite3's handling of non-aggregate expressions in GROUP BY queries as.. not fully satisfying. I think there really has to be a way to flag such queries as erroneous. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
