On 2016/07/15 2:45 PM, Jain, Punit wrote:
Clemens, thanks for the response. Since we are performing a join on a column
name of a table, we cannot give a fixed value. Is there any other way to
optimize join operations?
Hi Jain,
I think you may have missed the intent of Clemens' message - he is not
advising you to change your queries, he is suggesting you ensure your
virtual table implementation can handle queries of the kind:
... WHERE vt.somecolumn = <some fixed value>
Then internally, the SQLite query planner will will use that to do its
own internal nested join look-ups much faster. If this isn't supported,
the QP might walk your table every time.
If you are not familiar with how to support that WHERE-clause kind in
your VT implementation - refer the documentation or ask again, (but I
assume for now you are proficient in VT implementation) and that should
sort out the query speed.
Cheers!
Ryan
_______________________________________________
sqlite-users mailing list
[email protected]
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
