struct sqlite3_snapshot

 ... When a database connection begins a read transaction, that connection sees an unchanging copy of the database as it existed for the point in time when the transaction first started. Subsequent changes to the database from other connections are not ... 

 ... aggregate functions ALTER TABLE ANALYZE ATTACH DATABASE BEGIN TRANSACTION comment COMMIT TRANSACTION core functions CREATE INDEX CREATE TABLE CREATE TRIGGER CREATE VIEW CREATE VIRTUAL TABLE date and time functions DELETE DETACH DATABASE DROP INDEX DROP TABLE DROP TRIGGER DROP VIEW ... 

sqlite3_get_autocommit()

 ... If certain kinds of errors occur on a statement within a multi-statement transaction (errors including SQLITE_FULL, SQLITE_IOERR, SQLITE_NOMEM, SQLITE_BUSY, and SQLITE_INTERRUPT) then the transaction might be rolled back automatically. The only way to find out whether SQLite automatically rolled ... 

sqlite3_unlock_notify()

 ... For example, if connection X is waiting for connection Y's transaction to be concluded, and similarly connection Y is waiting on connection X's transaction, then neither connection will proceed and the system may remain deadlocked indefinitely. To avoid ... 

sqlite3_snapshot_recover()

 ... It is an error if there is already a read transaction open on the database, or if the database is not a WAL mode database. SQLITE_OK is returned if successful, or an SQLite error code otherwise. This interface is only ... 

sqlite3_blob_close()

 ... If an error occurs while committing the transaction, an error code is returned and the transaction rolled back. Calling this function with an argument that is not a NULL pointer or an open blob handle results in undefined behavior. Calling ... 

 ... The current writer concludes its transaction, OR The number of open read-transactions on the shared-cache drops to zero. Failed attempts to open new read-transactions return SQLITE_LOCKED to the caller. If the caller then calls sqlite3_unlock_notify() to register ... 

sqlite3_commit_hook(), sqlite3_rollback_hook()

The sqlite3_commit_hook() interface registers a callback function to be invoked whenever a transaction is committed. Any callback set by a previous call to sqlite3_commit_hook() for the same database connection is overridden. The sqlite3_rollback_hook() interface registers a callback function to be ... 

6. Avoiding Excessively Large WAL Files  ... Very large write transactions. A checkpoint can only complete when no other transactions are running, which means the WAL file cannot be reset in the middle of a write transaction. So a large change to a large database might result ... 

 ... ROLLBACK When a constraint violation occurs, an immediate ROLLBACK occurs, thus ending the current transaction, and the command aborts with a return code of SQLITE_CONSTRAINT. If no transaction is active (other than the implied transaction that is created on every ...