>> is it OK to use "threadsafe=2 and >> 2 connections" in my apps if the 2 threads may write at the same time?
>Yes. So I think "threadsafe=2 + more than 1 connection + busy_handler" is a good way to use. Another possible way is "threadsafe=1 and share 1 connection", but if thread 1 begins a transaction, then the SQL of thread 2 will also be executed within the transaction I guess. That may cause some unpredictable problems. BTW, if I use "threadsafe=0 and more than 1 connection", there will not be "database is locked" any more even if two threads writing at the same time, as mutex is disabled on core. Is it correct? -- Sent from: http://sqlite.1065341.n5.nabble.com/ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
