On 30 Jun 2010, at 12:32am, J. Rios wrote: > On Wed, Jun 30, 2010 at 12:13 AM, Simon Slavin <slav...@bigfraud.org> wrote: >> >> A good index would be >> >> name2, year, id >> >> That's all three columns in the same index, not three separate indexes one >> on each column. > > I did the test and EXPLAIN QUERY PLAN tells its going to use still the id > index and not the new created one and still its too slow.
Ooh. Interesting. I wonder which part of your SELECT is causing that. Perhaps the GROUP clause is changing how SQLite is working out what to do. Sorry for giving you useless information. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
