Error code
SQLite SQLITE_BUSY_SNAPSHOT
SQLITESQLITE_BUSY_SNAPSHOT
Database Error Code· An error code returned by a database server such as PostgreSQL or MySQL.
What it means
WAL snapshot conflict — a snapshot-isolated read cannot see a newer WAL frame.
How to fix it
- Commit or close the long-running read transaction so the WAL can be checkpointed.
- Avoid holding read transactions open across long periods when writers are active.
- Use BEGIN IMMEDIATE or BEGIN EXCLUSIVE when write ordering is required rather than relying on snapshot reads.
Not affiliated with SQLite. Answer summarized from the manufacturer's manual linked above; consult that source for the authoritative procedure.
More SQLite codes
- SQLITE_AUTHauthorization denied — an authorizer callback blocked the operation
- SQLITE_BUSYdatabase file is locked — another connection holds a shared or reserved lock
- SQLITE_CANTOPENunable to open the database file
- SQLITE_CONSTRAINTa constraint violation was raised — the write violates a database rule
- SQLITE_CONSTRAINT_FOREIGNKEYFOREIGN KEY constraint failed — the referenced row does not exist
- SQLITE_CONSTRAINT_UNIQUEUNIQUE constraint failed — a duplicate value was inserted
- SQLITE_CORRUPTthe database file is malformed — on-disk structure is damaged
- SQLITE_FULLthe database or disk is full — no space for the write
- SQLITE_IOERRan I/O error occurred on the disk
- SQLITE_LOCKEDa table in the database is locked — conflict within the same connection
- SQLITE_MISMATCHdatatype mismatch — the value type does not fit the affinity
- SQLITE_MISUSElibrary used incorrectly — the API was called in an invalid state