On 7 May 2010, at 11:14pm, Raeldor wrote: > Seriously... it can only use one index per query?
Sure. Because after using the first index it is no longer searching the table, it's searching a big collection of unindexed rows it got from the first search. There's no point in mindlessly making one index for each column you have in a table. Work out what WHERE and ORDER BY clauses you have on each search, and use those to work out which compound indices (ones which mention more than one column) will help you most. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
