Shortly after the release of SQLite version 3.8.8.1, Angelo Mottola reported an obscure but serious problem with SQLite 3.8.4 (from 10 months ago). This problem is still present in 3.8.8, so we intend to do a patch release to fix it. Please expect to see 3.8.8.1 within the next 24 hours.
So if you are about to upgrade to 3.8.8. Maybe you'll want to wait a day for 3.8.8.1 to come out. The problem found by Angelo involves a query that returns about 60 or more columns and that has both an ORDER BY and a LIMIT clause. Depending on the data, such queries might not order the results correctly. The error was first introduced by a performance optimization in SQLite 3.8.4 back in March of 2014, but was made much easier to hit by another optimization introduced in SQLite 3.8.7. "Much easier" is relative, of course. We never managed to hit it in the 168 million test cases we ran through SQLite for the 3.8.8 release. (We've since added new test cases and asser() statements to prevent a regression, of course.) The changes from 3.8.8 to 3.8.8.1 will be minimal. Expect the patch to be available within 24 hours. It's a bummer to learn of a long-standing problem like this just hours *after* a big release, rather than hours *before* when it can be addressed. But better late than never, I suppose. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-announce mailing list sqlite-announce@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-announce
