While the bulk INSERTs are being performed, I have a small shell
script that runs sqlite3 database.db "select count(*) from table" in
loop and sleeps 1 seconds between iterations.
Occasionally, sqlite3_step returns an error probably due to
concurrency issues. This is fine.
However, that puzzles me is that if PRAGMA cache_size = 0 is set on
dbh, return code of sqlite3_step is SQLITE_IOERR. If set to default,
2048, it is SQLITE_BUSY. If set to 128, it's a mix of those 2 codes.
After re-reading
http://www.sqlite.org/cvstrac/wiki?p=CorruptionFollowingBusyError, I
think the behavior I'm seeing is correct.
Sorry for the noise.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
