Areyou doing an sqlite3_finalize and checking to see that you actually
close the DB?
Philip Nick wrote:
Thanks for replying,
I have tried moving the Open/Close outside the mutex no change.
As for using our own mutex, we started with early versions of sqlite and had
to come up with our own solution. I was planning on looking into using the
built in mutex's, but first I need to solve the performance issues.
The only difference I can see between our code and the CLI is it uses
sqlite3_exec and a call back, while we do
sqlite3_prepare
Then we call sqlite3_column_count.
We loop through 0-num_col and call:
sqlite3_column_name
sqlite3_column_decltype
Then we do while(sqlite3_step() == SQLITE_ROW)
From my understanding the sqlite3_exec() is doing the same thing and sending
the info too the callback.
Any ideas?
Thanks
On Jan 17, 2008 5:09 PM, <[EMAIL PROTECTED]> wrote:
"Philip Nick" <[EMAIL PROTECTED]> wrote:
Greetings,
Currently I am using sqlite3 in a multi-process/multi-threaded server
setting.
I use a Mutex to ensure only one process/thread can access the database
at
one time.
The current flow of events:
Get Mutex
Open Database connection
Run Query
Close Database connection
Release Mutex
SQLite does the mutexing automatically (assuming you are using
version 3.5.0 or later).
--
D. Richard Hipp <[EMAIL PROTECTED]>
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
