On 7/26/16, Richard Hipp <d...@sqlite.org> wrote: > > Two possible fixes are: > > (1) Disable the new query algorithm introduced in 3.12. This does not > fix the cost estimate for the 3.11 algorithm, but as there are no > other reasonable competing algorithm choices, the 3.11 algorithm will > still win. The problem here is that there exist queries for which the > new 3.12 algorithm is desirable, and so disabling it will cause those > queries to run more slowly. > > (2) Invest the time and code needed for the query planner to make a > better cost estimate for the 3.11 algorithm in cases where the WHERE > clause can be checked using terms taken from only the index. This > will be a good deal of work, and will likely delay the release of > 3.14. > > I do not yet know which resolution we will take on this issue.
Resolution (2) is now on trunk and is in the latest Prerelease Snapshot. -- D. Richard Hipp d...@sqlite.org _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
