Sorry for answering my own email.
I had a bit of a breakthrough. Apparently compiled selects
sqlite3_prepare_v2 that live longer than the transaction are enough to
prevent the transaction from commiting. Each thread has it's own
connection to the DB.
With multiple threads, the order was:
prepar
Hi all,
I have a multithreaded app using 3.5.1 latest on the site.
I "BEGIN EXCLUSIVE TRANSACTION;"
Add some data and then
"COMMIT;"
The COMMIT sometimes returns SQLITE_ERROR but, the error message is
"Select still in progress". I was under the impression I was supposed
to get a "SQLITE_BUSY"
2 matches
Mail list logo