On Nov 25, 2007, at 2:21 PM, Roger Binns wrote:
I was under the impression that SQLite 3.5.2 is completely threadsafe,
meaning you can make any relevant API call in any thread. Examples of
things I thought are safe are:
- - Using statements from the same connection in different threads
- - Calling step on a statement in one thread and then calling it
again in
another thread
- - Doing some blob i/o in one thread and then doing more in another
The FAQ currently says it is somewhat safe.
http://www.sqlite.org/faq.html#q6
Is the FAQ out of date?
SQLite is completely threadsafe in 3.5.2. But that does not mean
that running SQLite will magically fix threading bugs in Linux 2.4
kernels or in GLIBC. The FAQ warns you to beware these problems.
By "threadsafe" in 3.5.2, that means you can call SQLite simultaneously
from different threads using the same database connection. SQLite
contains its own mutexes to serialize access.
D. Richard Hipp
[EMAIL PROTECTED]
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
