Re: [sqlite] Multithreads access the same database resulting in database is locked error

2008-03-25 Thread Ken
I don't see any error handling in your code for SQLITE_BUSY... Also, Depending upon the odbc driver your using, you might want to change the begin to a "begin immediate" causing the lock to be taken out at the begin vs later on... Xuanvinh Vu <[EMAIL PROTECTED]> wrote: I did check and I have

Re: [sqlite] Multithreads access the same database resulting in database is locked error

2008-03-25 Thread Xuanvinh Vu
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 causes the DB to block me before should have

Re: [sqlite] Multithreads access the same database resulting in database is locked error

2008-03-25 Thread Igor Tandetnik
Xuanvinh Vu <[EMAIL PROTECTED]> wrote: > Here is what the error looks like... > > [1436] 25 Mar 16:24:24 OnEveryHour: Failure occurred while updating > the OneMonth table. Exception: System.Data.Odbc.OdbcException: ERROR > [HY000] database is locked (5) > What does the error code 5 stands for? SQ

[sqlite] Multithreads access the same database resulting in database is locked error

2008-03-25 Thread Xuanvinh Vu
Here is what the error looks like... [1436] 25 Mar 16:24:24 OnEveryHour: Failure occurred while updating the OneMonth table. Exception: System.Data.Odbc.OdbcException: ERROR [HY000] database is locked (5) What does the error code 5 stands for? Also I started getting the errors when I starte