bert hubert wrote:
My question is: can sqlite3_step return SQLITE_BUSY, without ever calling my
handler? It certainly does so in my application, which is written in single
threaded c++ and runs under linux 2.6.10-rc2, Debian sid, with sqlite
3.0.8. It happens with 3.0.7 as well.
SQLite will return SQLITE_BUSY instead of calling the busy handler in
some circumstances in order to avoid deadlocks. But if you start your
transactions using
BEGIN EXCLUSIVE;
instead of just "BEGIN", then the deadlocks are impossible and you
you will never get an SQLITE_BUSY return unless your busy handler
callback returns 0.
--
D. Richard Hipp -- [EMAIL PROTECTED] -- 704.948.4565
