3 ms·
SQLite only allows one writer at a time. Attempts at multiple DML logins will not block until successful, but simply fail. The allowed writer can also impact r
by chasil 4y ago
SQLite only allows one writer at a time. Attempts at multiple DML logins will not block until successful, but simply fail.
The allowed writer can also impact readers, depending on the WAL mode setting.
For DSS uses, where a data store is published once a day, SQLite is wonderful. For OLTP, look elsewhere.
- sgbeal 4y ago> Attempts at multiple DML logins will not block until successful, but simply fail. sqlite has a "busy handler" mechanism which tells it how to respond to blocks and most apps use the builtin one with which they can tell it "wait for X milliseconds before failing on a lock." The Fossil SCM (https://fossil-scm.org https://fossil-scm.org), the SCM in which sqlite itself is hosted, is an sqlite application which serves thousands of users per day, many of them in write transactions. Its forum is a separate sqlite3 instance. sqlite3's own forum is another... all of those serve many users, many of whom are writing, and in 14 years of using/contributing to fossil-scm.org, almost on a daily basis, i've hit exactly two locking errors.