Hi Simon,
Yep, I too find the Query Plan's easier to read (sometimes I even think
I understand bits of them!)
I do expect SQLite to get slower with an Order By - it has more work to
do after all, but I thought I'd ask for this one because it's slowing
down by almost two orders of magnitude (a bit less in 3.23.0) when I add
the ORDER which seems quite a lot for ordering 86 items. I have no idea
what the EXPLAIN /says/, but I can see it's very different between the
two of them so this suggested the QP might be going astray.
Even if I delete all the indexes it's using, it still evidences, though
the timings are higher (0.1s without, 0.2s with ORDER BY/LIMIT).
Cheers,
Jonathan
On 2018-03-22 22:13, Simon Slavin 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
