On Mon, Dec 15, 2014 at 06:23:31PM +0700, Dan Kennedy wrote: > It's tricky. As you say, xBestIndex() will currently be invoked > twice - once with no constraints usable and once with both "b.id=?" > and "b.linkid=?" usable. I guess the reason it is not invoked in the > other ways you suggest is that that strategy might conceivably > require a huge number of xBestIndex() calls if there were more than > a few other tables in the join.
Perhaps there should be a method by which distinct indices could be expressed by the virtual table to the SQLite3 query optimizer. One possible compromise would be to call xBestIndex() with each constraint, then once more with all of them. Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
