There can be only one thread that has an exclusive write lock on the database.
Most likely this is a bug in your application.
Heres what I do for my multi threaded app:
1. All transactions use "begin immediate" (that way I don't do a bunch of
work only to find the db locked later).
2. The
I didnt realize that it could cause livelocks. Thank you for bringing that to
my attention. It still doesnt explain why the database stays locked. I could
just ignore the error and wait to update the database the next time the thread
runs again. What I want to know is why once I got the excepti
Xuanvinh Vu <[EMAIL PROTECTED]> wrote:
> I did check and I have all the BEGINs and COMMITs. I understand that
> by default the sqlite busy signal is given right away so what I do is
> I wait till the next interval elapses to try to update the DB again
> by that time whatever the transaction that ca
3 matches
Mail list logo
