On 1 Aug 2012, at 8:25pm, Udi Karni <uka...@gmail.com> wrote: > - only 2 processes > - only for simple full scans where the block range can be divided in two > - only when there is no ORDER/GROUP BY where sub results from the 2 threads > have to be combined
Premature optimization ? SQLite, just by itself with default compilation and a set of PRAGMAs which suit your requirements, is extremely fast. Write your application first, and only if it turns out to be too slow worry about clever tricks like that. And if it really is too slow, and you want tricks like the above, it's probably better to switch to a different DBMS which will itself speed things like the above up because it does caching and other such tricks. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
