Martin Alfredsson wrote:
Is this correct ?
My program calls:
sqlite3_prepare(...)
sqlite3_step(...)
Here another process writes to the database sqlite3_exec(...)
sqlite3_finalize(...)
Now my program will fail with SQLITE_BUSY (5) when
accessing the database.
If I dont terminate the other process restaring my program
will not help since it will get SQLITE_BUSY (5) all the time.
Is there a way to avoid this,
Can I stop another process from being able to write to the
db while my program is between a _step/_finalize ?
(Avoiding "long" SELECTs is hard due to lots of data).
/Martin
ma1999ATjmaDOTse
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
Only one user can write to an Sqlite database at any time. The logic of
your application has to enforce that "serialization" or "single
streaming" in some way.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
