Hi,

>> But more simply and importantly, SQLite only commits to the file when 
>> a transaction is completed.  (There's an implicit transaction around 
>> every INSERT / UPDATE, etc. if you don't specify a transaction 
>> yourself.) I've seen significant performance increases by wrapping 
>> repeated modifications of large datasets with transactions (by using 
>> the SQL statements "BEGIN;" and "END;"), which allows the disk access 
>> to be

>I've read this FAQ before on the sqlite site, but it doesn't apply to my
>case: I've a database which is static, it is built from scratch from time
>to time and I simply need to perform a lot of SELECT on the db.

A trivial suggestion, but this usually comes from absence of
indexes or sql queries which fail to use existing indexes. I.e.
you have a good reason to check how your sql queries are
compiled into sqlite virtual machine instructions.

This was discussed in the sqlite list from time to time.

Mikhail


-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners