[sqlite] Reasons for SQLITE_BUSY

Hello,

I am accessing the same database from different threads. Each thread has
its own connection. I have set the busy timeout for each connection to
5000 milliseconds.

However, in some testcases I still get SQLITE_BUSY errors from
sqlite3_step. Moreover, the whole testcases run in much less than 5
seconds, to apparently sqlite does not even try to wait for the lock to
disappear.

Can someone explain to me under which circumstances SQLITE_BUSY is returned
immediately, without calling the busy handler first? Hopefully this will
give me an idea of where to look for the problem...

In case it matters: I'm using the Python apsw wrapper compiled against
CVS SQLite from Jul 27th.

Best,

   -Nikolaus

-- 
 ÂTime flies like an arrow, fruit flies like a Banana.Â

  PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6  02CF A9AD B7F8 AE4E 425C

_______________________________________________
sqlite-users mailing list
sqlite-users@xxxxxxxxxx
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users