On 10/10/2012 10:09 PM, Hamish Allan wrote:
On 10 October 2012 16:07, Dan Kennedy<danielk1...@gmail.com> wrote:
On 10/10/2012 10:01 PM, Ryan Johnson wrote:
On 10/10/2012 10:49 AM, Dan Kennedy wrote:
The easiest workaround is probably to use a temp table to store the
unaggregated results of the FTS query.
What about a nested query?
Actually that will cause a problem too, as the optimizer will
flatten the sub-query.
Is there any way to tell the optimiser to use a temporary table for
the sub-select rather than flattening the sub-query?
I don't think there is. It's this optimization causing the trouble:
http://www.sqlite.org/optoverview.html#flattening
You could change your query so that it doesn't qualify for that
optimization I suppose. Easiest way would be to append
"LIMIT -1 OFFSET 0" to the end of it. Of course, there is no
guarantee that a future version of SQLite will not see through
that, apply the optimization and hit the limitation.
Dan.
Thank you both for your replies.
H
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
