Removing "COUNT(*) AS count" and "GROUP BY class" and doing it in-program shaved ~10% off of the time. I'll keep it. :) ~Seth
On Aug 4, 2011, at 11:30 AM, Eduardo Morras wrote: > > Oks, another let's try another thing/think. > > Try the select without the COUNT(*): > > SELECT class FROM data_r JOIN data USING (rowNum) WHERE 57 < col0min > AND col0max < 61 AND 52 < col1min AND col1max < 56 AND 66 < col2min > AND col2max < 70 AND 88 < col3min AND col3max < 92 AND 133 < col4min > AND col4max < 137 AND 57 < col0 AND col0 < 61 AND 52 < col1 AND col1 > < 56 AND 66 < col2 AND col2 < 70 AND 88 < col3 AND col3 < 92 AND 133 > < col4 AND col4 < 137 AND 81 < col5 AND col5 < 85 GROUP BY class; > > In some rdbms (don' know in sqlite), count, avg, sum, etc... implies > a table scan, making the select very slow. > > HTH > > > _______________________________________________ > 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
