2011/7/26 Black, Michael (IS) <michael.bla...@ngc.com> > > Turns out the if you include the primary key in an index it doesn't use the > triple index but uses the primary key instead. And analyze doesn't change > it. > > This is with version 3.7.5 > > Not sure about the primary index , because with my data and 3.7.6.2 it still uses the index, but visits every entry.
the fast one: WHERE a=10 and b=20 and c> 1000000 explain query plan > SEARCH TABLE abctable USING COVERING INDEX idxabc (a=? AND b=? AND c>?) (~2 rows) the "slow" one WHERE a=10 and b=20 and id>1000000 explain query plan > SEARCH TABLE abctable USING COVERING INDEX idxabid (a=? AND b=?) (~3 rows) I assume the optimizer could use the following "plan" ... COVERING INDEX idxabid (a=? AND b=? AND rowid>?) but it didn't. Maybe for a reason... Max _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
