Post Re: SQLite concurrency and why you should care about it

Re: SQLite concurrency and why you should care about it In SQLite, transactions by default start in “deferred” mode. This means they do not take a write lock until they attempt to perform a write. You get SQLITE_BUSY when transaction #1 starts in read mode, transaction #2 starts in write mode, and then transaction #1 attempts to upgrade from read to write mode while transaction #2 still holds the write lock. The fix is to set a busy_timeout and to begin any transaction that does a write (any write, even if it is not the first operation in the transaction) in “immediate” mode rather than “deferred” mode. https://zeroclarkthirty.com/2024-10-19-sqlite-database-is-lo... asa400, 7 hours ago