Re: [sqlite] Reasons for SQLITE_BUSY

2009-07-31 Thread Edzard Pasma
--- nikol...@rath.org wrote: > "Edzard Pasma" writes: >> --- nikol...@rath.org wrote: >>> "Igor Tandetnik" writes: Nikolaus Rath wrote: > I am accessing the same database from different threads. Each > thread > has

Re: [sqlite] Reasons for SQLITE_BUSY

2009-07-31 Thread Nikolaus Rath
"Edzard Pasma" writes: > --- nikol...@rath.org wrote: >> "Igor Tandetnik" writes: >>> Nikolaus Rath wrote: I am accessing the same database from different threads. Each thread has its own connection. I have set the

Re: [sqlite] Reasons for SQLITE_BUSY

2009-07-30 Thread Edzard Pasma
--- nikol...@rath.org wrote: > "Igor Tandetnik" writes: >> Nikolaus Rath wrote: >>> I am accessing the same database from different threads. Each thread >>> has its own connection. I have set the busy timeout for each >>> connection to 5000 milliseconds.

Re: [sqlite] Reasons for SQLITE_BUSY

2009-07-29 Thread Nikolaus Rath
"Igor Tandetnik" writes: > Nikolaus Rath wrote: >> I am accessing the same database from different threads. Each thread >> has its own connection. I have set the busy timeout for each >> connection to 5000 milliseconds. >> >> However, in some testcases I

Re: [sqlite] Reasons for SQLITE_BUSY

2009-07-29 Thread Igor Tandetnik
Nikolaus Rath wrote: > I am accessing the same database from different threads. Each thread > has its own connection. I have set the busy timeout for each > connection to 5000 milliseconds. > > However, in some testcases I still get SQLITE_BUSY errors from > sqlite3_step.

[sqlite] Reasons for SQLITE_BUSY

2009-07-29 Thread Nikolaus Rath
Hello, I am accessing the same database from different threads. Each thread has its own connection. I have set the busy timeout for each connection to 5000 milliseconds. However, in some testcases I still get SQLITE_BUSY errors from sqlite3_step. Moreover, the whole testcases run in much less