> I usually seem to be wrong when I try to help here, but I keep trying. > > My guess is that SQLite uses only one index per query (or per table per > query or something like that), and so has to do a whole bunch of full > table scans (or at least full scans of the remaining rows). >
huum if it's true it's a big disaster :( > Maybe you need a query like: > > > select id from (select id from hash where > > x1_y1 BETWEEN #randomnumber1 AND (#randomnumber1 + 20)) where x1_y2 BETWEEN > #randomnumber4 AND (#randomnumber4 + 20) > > > nested many more levels deep. This might allow using all the indices. i will try thanks _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
