You need to be prepared to get a busy status after each Sqlite3_step.
If you launch a sqlite3_step while a transaction which is executing an
INSERT or UPDATE is current, you will get an SQLITE_BUSY. If you get a
BUSY, try again until the condition clears.
Igor Mironchick wrote:
Hi, guys.
I have some questions about multithreading in SQLite:
a) If one thread "BEGIN" and after that another thread try to "BEGIN".
What will with the second thread? How I understand there is nothing
wrong. Is it right?
b) The same one only when second thread "BEGIN" after first thread
"BEGIN" and "INSERT" but before "COMMIT"? Here, how I understand, second
thread will get "SQLITE_BUSY" and have nothing to read?!?!
P.S. First thread is a writer and a reader and the second one is a
reader only.
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
