> Therefore, SQLite
> returns SQLITE_BUSY for the first process, hoping that this will
> induce the first process to release its read lock and allow the
> second process to proceed.
[snip]
> In short, you can poke at a SQLITE_BUSY state for a bit, but fairly
> soon you should give
, 16 October 2009 2:00 PM
To: j...@kreibi.ch; General Discussion of SQLite Database
Subject: Re: [sqlite] Exception writing to database from multiple
processes
Yes, sqlite CAN deadlock. It is a weakness of the locking model combined
with a weakness in the transaction model. The big problem is that
y, especially if you
have a long running process, like a sync.
John
-Original Message-
From: sqlite-users-boun...@sqlite.org
[mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Jay A. Kreibich
Sent: Friday, October 16, 2009 12:38 AM
To: General Discussion of SQLite Database
Subject: Re: [sq
On Thu, Oct 15, 2009 at 10:57:11PM -0400, Pavel Ivanov scratched on the wall:
> You're definitely talking about some bug in your application or some
> misunderstanding about how SQLite should work. SQLite by itself never
> causes any deadlocks.
As I understand it, that's not exactly true. SQLit
Of Pavel Ivanov
Sent: Thursday, October 15, 2009 10:57 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Exception writing to database from multiple processes
You're definitely talking about some bug in your application or some
misunderstanding about how SQLite should work
; [mailto:sqlite-users-boun...@sqlite.org] On Behalf Of Pavel Ivanov
> Sent: Thursday, 15 October 2009 9:53 PM
> To: General Discussion of SQLite Database
> Subject: Re: [sqlite] Exception writing to database from multiple processes
>
>> However, when it is run
>> inside a
qlite-users-boun...@sqlite.org [mailto:sqlite-users-boun...@sqlite.org]
On Behalf Of Pavel Ivanov
Sent: Thursday, 15 October 2009 9:53 PM
To: General Discussion of SQLite Database
Subject: Re: [sqlite] Exception writing to database from multiple processes
> However, when it is run
>
> However, when it is run
> inside an Application Pool with multiple worker processes, the database
> soon becomes locked and cannot be written to by any of the worker
> processes.
You mean your application hangs? None of workers can write to database
and nothing else happens in application? Nobod
8 matches
Mail list logo
