db_lock: Start a write transaction
In liteq: Lightweight Portable Message Queue Using 'SQLite'
db_lock R Documentation
Start a write transaction
Description
We use BEGIN IMMEDIATE for every write. A deferred transaction
(plain BEGIN) that reads first and writes later might fail with
"database is locked" right away, without waiting for the busy
timeout, because SQLite cannot wait there without risking a deadlock.
Unlike BEGIN EXCLUSIVE, BEGIN IMMEDIATE does not block readers.
Usage
db_lock(con, retry = TRUE)
Arguments
con
DB connection.
retry
Whether to retry if the database is locked.
Details
If retry is TRUE, then we keep trying until we get the lock.
Each try waits for the busy timeout, so this does not spin.
liteq documentation built on Nov. 5, 2026, 5:07 p.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
| db_lock | R Documentation |
Start a write transaction
Description
We use BEGIN IMMEDIATE for every write. A deferred transaction
(plain BEGIN) that reads first and writes later might fail with
"database is locked" right away, without waiting for the busy
timeout, because SQLite cannot wait there without risking a deadlock.
Unlike BEGIN EXCLUSIVE, BEGIN IMMEDIATE does not block readers.
Usage
db_lock(con, retry = TRUE)
Arguments
con |
DB connection. |
retry |
Whether to retry if the database is locked. |
Details
If retry is TRUE, then we keep trying until we get the lock.
Each try waits for the busy timeout, so this does not spin.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.