--- [EMAIL PROTECTED] wrote:
> True enough, in general. But with SQLite 3.5, access to each
> database connection is serialized. So even though the interface
> allows you to have 20 different threads all doing sqlite3_exec()
> on the same connection at the same time, the SQL statements are
> still being processed one by one, regardless of how many CPUs
> you devote to the task.
This is perfectly reasonable for an embedded database using a single file.
At least access to sqlite connections to different databases can
still be done in parallel on different threads.
The minor slowdown due to mutexes and serialization on a single database
is more than made up by the vastly simplified rules to using the API
in a multi-threaded scenario.
It also removes the burden from the sqlite language wrappers - some of
which made invalid assumptions about sqlite connection thread usage with
pre-3.5 versions which were the source of many random crashes.
____________________________________________________________________________________
Tonight's top picks. What will you watch tonight? Preview the hottest shows on
Yahoo! TV.
http://tv.yahoo.com/
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
