On Tue, Oct 5, 2010 at 4:55 AM, Jay A. Kreibich <j...@kreibi.ch> wrote:
> On Mon, Oct 04, 2010 at 07:25:05PM -0700, Dustin Sallings scratched on the > wall: > > > The main difference between =1 and =2 is that =2 assumes you more or > less know what you're doing and will either lock a database handle as > you pass it between threads or you'll keep it private to a thread. > > =1 is designed to be more or less idiot proof, and will simply not > let you do something stupid with a database handle, like have two > threads try to execute two different statements at the same time. > > What if two therad make insert or update then commit, what is happen to the second thread after the first made commit?. > Either way, any multi-threaded program requires something other than =0. > > In your case, it sounds like =2 would be sufficient, but if you're > not looking for every millisecond of performance you can find, the > default =1 might be easier and safer. > -- Zaher Dirkey _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
