> On Aug 18, 2017, at 11:29 PM, Dan Kennedy <danielk1...@gmail.com> wrote: > > On 08/18/2017 05:39 AM, Jens Alfke wrote: >> I believe I may have found a bug in SQLite 3.18. I've got a query that >> returns a correct result set when there are no indexes in the database, but >> returns an incorrect result set if recompiled after an index has been added. >> The incorrect result set has no collation applied, so the problem seems to >> be that when SQLite uses the index to optimize the query, it forgets to >> apply collation when grouping and ordering the results, so the results are >> in uncollated order as they appeared in the index. > > Thanks for reporting this. Bug ticket and fix now here: > > http://www.sqlite.org/src/info/e20dd54ab0e43838 > <http://www.sqlite.org/src/info/e20dd54ab0e43838> > http://www.sqlite.org/src/info/37e1900880b70be6 > <http://www.sqlite.org/src/info/37e1900880b70be6> W00t! I feel proud to have discovered an actual bug in SQLite. Are there nerd merit badges available for this? ;-) (And thanks for the quick fix!)
—Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
