On Dec 4, 2007, at 11:47 PM, Dennis Cote wrote:
Dan wrote:
This is failing because the internal representation of the database
schema used by the first connection has not yet been updated to
include the changes made in step 4 by the second connection.
After the sqlite3_prepare() in step 6 fails with the "no such table"
error, SQLite realises that it may be using an old schema version and
discards it. The new schema will be loaded fresh from the database
next time a call is made to sqlite3_prepare().
So the easiest fix is just to retry the sqlite3_prepare().
Doesn't sqlite do this automatically now if the OP were to switch
to the new sqlite3_prepare_v2 API instead of using the
sqlite3_prepare API?
No. sqlite3_prepare_v2() behaves the same way in this case.
Dan.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
