I was trying to force the use of a multi-column index. Will have a better look and see what is going on here. For now I get best performance with a 2-stage approach with the use of a intermediate temp table. Will post the exact details of this later.
RBS > If neither index individually offers a performance boost, it's possible a > single multi-column index might be better. > Sam > > > On Thu, Sep 17, 2009 at 3:43 PM, Bart Smissaert > <bart.smissa...@gmail.com>wrote: > >> Have tried INDEXED BY and it does indeed work and force the use of the >> specified index. >> It didn't however make the query faster, so maybe the SQLite plan >> generator is better than I thought! >> >> RBS >> >> >> > _______________________________________________ > 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
