My guess is that you will find your problem in the way file locking is
implemented on your system. Is there a global file lock rather than
locks associated with each file? A simple test program will resolve the
issue.
Mark Brown wrote:
Hi Andre-
After rereading your post, I wanted to confirm something. In your example
below, are thread1 and thread2 connected to the same database, or different
databases? In my scenario, the threads are connected to different
databases, so I'm not sure if it is the same situation.
Thanks,
Mark
-----Original Message-----
From: Andre du Plessis [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 15, 2007 5:05 AM
To: sqlite-users@sqlite.org
Subject: RE: [sqlite] SQLITE_BUSY error in multi-threaded environment
Being a newbie to SQLite I've had the same problems working
with SQLite
so maybe I can help,
It does not matter how well your database is synchronized, a common
pitfall I had was that I would have a query object with an open cursor
which prevents any other statement from committing to the database.
So for example:
THREAD1 THREAD2
LOCK
QUERY
UNLOCK LOCK
(Step through query) BEGIN TRANSACTION
INSERTS
COMMIT <- SQLite busy error here
UNLOCK
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
