I want to use SQLite with only one user executing queries sequentially , so
I don't need locking. Is there a simple way to completely disabling
locking?
Specific instructions if possible please, thanks...
There are two kinds of locks.
First one is a file lock, as in functions returning SQLITE_BUSY. From what I
understand, if you do execute queries sequentially, or serialize the queries
from threads yourself. You won't be experiencing any file lockings.
The second is the database lock, as in functions returning SQLITE_ERROR.
This could only happen when you didn't write your code correctly. For
instance, if you forgot to finalize one prepared INSERT statement, and tried
to prepare another INSERT statement right behind, you'll get SQLITE_ERROR,
while sqlite3_reset will return SQLITE_LOCKED.
Queries must be executed sequentially on a single sqlite connection. It's
not your choice. If you need to execute parallel queries, you have to open
another connection and handle busy status. Locking is not a feature for you
to disable. It's a fact that you can't read or write before another writing
process is finished.
Best regards,
He Shiming
-----------------------------------------------------------------------------
To unsubscribe, send email to [EMAIL PROTECTED]
-----------------------------------------------------------------------------
