> Marcus Grimm wrote:
>> I skipped to use the busy handler and the busy timeout and do
>> the handling by my selve. typically like:
>
> Are you aware that your code is very similar to the default SQLite busy
> handler if you set a busy timeout? I'd argue that the one shipped with
> SQLite is
Marcus Grimm wrote:
> I skipped to use the busy handler and the busy timeout and do
> the handling by my selve. typically like:
Are you aware that your code is very similar to the default SQLite busy
handler if you set a busy timeout? I'd argue that the one shipped with
SQLite is better since it
Marco Bambini <[EMAIL PROTECTED]> wrote:
> I have several threads inside an application and each thread opens a
> connection to the same database.
> The application has been compiled with SQLITE_THREADSAFE = 1.
> One of the threads (just one) open another database connection to the
> same database
Hi,
I also spend some time with a similar application and sqlite
is doing quite well so far, however you will get BUSY states
and LOCK states under "normal" condition and you will need
to handle them.
I skipped to use the busy handler and the busy timeout and do
the handling by my selve.
I have several threads inside an application and each thread opens a
connection to the same database.
The application has been compiled with SQLITE_THREADSAFE = 1.
One of the threads (just one) open another database connection to the
same database used by ALL threads for all the writing
5 matches
Mail list logo
