John Stanton <[EMAIL PROTECTED]> wrote:
You need to be prepared to get a busy status after each Sqlite3_step.
Not really. Only the very first sqlite3_step after a prepare or reset can get SQLITE_BUSY. If it succeeds, the connection has acquired a SHARED lock and subsequent steps are guaranteed not to run into concurrency problems.
Igor Tandetnik
----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
