On 22 Dec 2010, at 2:41pm, Philip Graham Willoughby wrote: > You would need to reintroduce practically everything you think you can get > rid of if you wish to ensure that there is only one process and you are > intending to provide a facility for two transactions to be active > concurrently.
I agree with your statement but I don't think it's worth doing those things. SQLite can still be light, and it's okay for one connection to lock all the others out until it is finished. As long as you support the various types of transaction locking (i.e. IMMEDIATE, etc.) and return the appropriate result codes, you're okay. Simon. _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
