... A VACUUM will fail if there is an open transaction on the database connection that is attempting to run the VACUUM. Unfinalized SQL statements typically hold a read transaction open, so the VACUUM might fail if there are unfinalized SQL ... 

2.4. B-Tree Cursors A prepared statement can have zero or more open cursors. Each cursor is identified by a small integer, which is usually the P1 parameter to the opcode that uses the cursor. There can be multiple cursors open on the same ... 

sqlite3_total_changes(), sqlite3_total_changes64()

These functions return the total number of rows inserted, modified or deleted by all INSERT, UPDATE or DELETE statements completed since the database connection was opened, including those executed as part of trigger programs. The two functions are identical except ... 

6. Result Code Meanings  ... The SQLITE_READONLY_RECOVERY error code indicates that a WAL mode database cannot be opened because the database file needs to be recovered and recovery requires write access but only read access is available. (266) SQLITE_IOERR_READ The SQLITE_IOERR_READ error code is an ... 

sqlite3_db_cacheflush()

If a write-transaction is open on database connection D when the sqlite3_db_cacheflush(D) interface invoked, any dirty pages in the pager-cache that are not currently in use are written out to disk. A dirty page may be in ... 

 ... 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 ... 

1.2. Untrusted SQLite Database Files  ... Invoke sqlite3_db_config(db,SQLITE_DBCONFIG_TRUSTED_SCHEMA,0,0) on each database connection as soon as it is opened. Run the PRAGMA trusted_schema=OFF statement on each database connection as soon as it is opened. Compile SQLite using the -DSQLITE_TRUSTED_SCHEMA=0 compile-time ... 

 ... If database connection X is holding a read transaction, it is possible that some other database connection Y might change the content of the database while X's transaction is still open, however X will not be able to see ... 

sqlite3_file_control()

 ... If the second parameter (zDbName) does not match the name of any open database file, then SQLITE_ERROR is returned. This error code is not remembered and will not be recalled by sqlite3_errcode() or sqlite3_errmsg(). The underlying xFileControl method might also ... 

 ... Changing the value of this variable while a database connection is open can result in a corrupt database. It is not safe to read or modify this variable in more than one thread at a time. It is not safe ...