--- 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
"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
--- 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.
"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
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.
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
6 matches
Mail list logo