On Tuesday, 15 August, 2017 09:52, Jens said: >> On Aug 15, 2017, at 8:12 AM, Bob Friesenhahn <[email protected]> >> wrote:
>> Notice that adding a 'where' clause has caused the order to be >>reversed from what was requested in the query. Why is this and what >>can I do to correct it? >It’s actually not reversed; the ordering looks random. So it appears >the ORDER BY wasn’t applied. Huh. >… Actually, the docs for group_concat do say "The order of the >concatenated elements is arbitrary.” :-/ Well, the documentation is incorrect. The ordering is entirely deterministic. The items presented to the aggregate are concatenated in the order in which they are presented to the aggregate function, and this ordering is determined solely by the traversal order of the underlying table from which the data is drawn. --- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. _______________________________________________ sqlite-users mailing list [email protected] http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
