Igor - ok I tried this, and now I am getting SQLITE_BUSY returned when I try
to sqlite3_exec my "BEGIN IMMEDIATE" statement. So I then put that in a
do-while( rc == SQLITE_BUSY) loop, and now my first thread is getting
SQLITE_BUSY returned when it tries to execute the 1-line INSERT statement
(with
Dave Brown <[EMAIL PROTECTED]> wrote:
Hi all - I am seeing a strange problem where I have multiple threads
trying to both do writes to the database, and one thread gets back an
immediate SQLITE_BUSY even though *both* have set the busy handler to
10 seconds, and the write operation is much much f
2 matches
Mail list logo
