When I saw this post I just assumed there wasn't a sufficient index to handle the select and the order by.
Curious about the suggestion of adding + to the order by first term. On Thu, Mar 22, 2018 at 3:14 PM Simon Slavin <slav...@bigfraud.org> wrote: > On 22 Mar 2018, at 10:09pm, Jonathan Moules <jonathan-li...@lightpear.com> > wrote: > > > Sure; I didn't include them because the only difference is the last > line, and that just seems to be the standard "ordering" line. I figured the > explain was more useful as a lot has changed in that. > > I find EXPLAIN QUERY PLANs easier to read (probably unlike the development > team who understand things at the level of EXPLAIN). > > The situation as you describe it in the above post is that your query gets > /slower/ when you add an ORDER BY clause. This is not expected, and does > not suggest anything wrong with SQLite. > > Simon. > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
