> Did something in the documentation make > you think SQLite wouldn't use a > multi-column index unless you forced it ?
No, but I just noticed it didn't use the index I thought would be best. As it turned out it looks I was wrong in that that index didn't give the quickest result. RBS > > On 18 Sep 2009, at 1:51pm, bartsmissa...@blueyonder.co.uk wrote: > >> I was trying to force the use of a multi-column index. > > Did something in the documentation make you think SQLite wouldn't use > a multi-column index unless you forced it ? There is rarely any point > in forcing any particular index. The part of SQLite which determines > which index to use is very good at working out which index is best for > the operation it's doing. > > Simon. > _______________________________________________ > 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