On Fri, Jan 30, 2015 at 4:38 PM, Dan Kennedy <danielk1...@gmail.com> wrote:

> On 01/29/2015 02:29 AM, farkas andras wrote:
>> [...] but searches based on ROWID are atrociously slow and hog massive
>> amounts of memory [...]
> Looks like range constraints on rowids were only taken into account when
> there was also a MATCH term in the WHERE clause. Now fixed here:
>   http://www.sqlite.org/src/info/85dc12625d300f
> The fix should be in 3.8.9.

Just curious Dan. The tests added do not seem to check the query plans
despite the report being about a performance issue. I only skimmed them,
and I'm unfamiliar with TCL and the exact specifics of SQLite testing, so I
could well have missed them, but I do recall seen other perf tests checking
execution plans, in addition to checking correctness. Did I miss them?
Thanks, --DD
sqlite-users mailing list

Reply via email to