2 ms·
It appears to be safe, but potentially slow, assuming you have working fcntl() locking, that is, for example, not using NFS. And you have to handle SQLITE_BUSY
by tyingq 5y ago
It appears to be safe, but potentially slow, assuming you have working fcntl() locking, that is, for example, not using NFS. And you have to handle SQLITE_BUSY or set a timeout. More in their FAQ, Q5: https://www.sqlite.org/faq.html#q5 https://www.sqlite.org/faq.html#q5
There's also "BEGIN CONCURRENT" with WAL mode: https://sqlite.org/src/doc/begin-concurrent/doc/begin_concurrent.md https://sqlite.org/src/doc/begin-concurrent/doc/begin_concur...
- stavros 5y agoInteresting, thanks! EDIT: Looks like it has a simple read/write lock, which isn't great for write-heavy workloads, but that's up to the application developer to decide. BEGIN CONCURRENT looks great, however.