Lee Crain <[EMAIL PROTECTED]> wrote:
Igor,
I did say "controlled" concurrency.
I'll rephrase question 3.
3) Would use of a MUTEX to avoid the dreaded "SQLite busy" condition
be a
good solution?
Wouldn't it prevent multiple concurrent readers? That's usually
something you want.
Or is some other method of avoiding a busy condition
recommended?
You can start every writing transaction with BEGIN EXCLUSIVE. In
addition, you can use sqlite3_busy_timeout to set the timeout to a very
large value (making the timeout so long that it can be considered
infinite for practical purposes). With these two fixes, the behavior
will be similar to that of a mutex-based solution, except that you would
still allow concurrent readers.
Igor Tandetnik
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
