sqlite3_step -> Jan 8 16:50:49 | CRITICAL | test3_proc | Error: Error
fetching cursor=[sel_proc] db=[tst_sqlitethrd.db] rc=[5] msg=[database is
locked]
sqlite3_finalize -> Jan 8 16:50:49 | CRITICAL | test3_proc | Error: Error
closing cursor=[sel_proc] db=[tst_sqlitethrd.db] rc=[5] msg=[database is locked]
sqlite3_reset -> Jan 8 16:50:49 | CRITICAL | test3_proc | Error: Error
resetting cursor=[sel_proc] db=[tst_sqlitethrd.db] rc=[21] msg=[database is
locked]
Ok I think I know.. the reset should not have been called. What should one do
if you get a SQLITE_BUSY on finalizing ????
[EMAIL PROTECTED] wrote: Ken wrote:
> Found the issue:
>
>
> Called sqlite3_finalize after recieving a SQLITE_BUSY on on sqlite3_step,
> then you get a segfault and all sorts of errors, glibc related.
>
Unable to reproduce, even before the most recent corrections to
sqlite3_prepare_v2(). Please provide additional information.
http://www.sqlite.org/cvstrac/chngview?cn=3577
--
D. Richard Hipp
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
