... If the statement is a COMMIT or occurs outside of an explicit transaction, then you can retry the statement. If the statement is not a COMMIT and occurs within an explicit transaction then you should rollback the transaction before continuing ... 

 ... ACID transactions using BEGIN, COMMIT, and ROLLBACK Nested transactions using SAVEPOINT, RELEASE, and ROLLBACK TO Subqueries, including correlated subqueries Up to 64-way joins LEFT, RIGHT, and FULL OUTER JOINs DISTINCT, ORDER BY, GROUP BY, HAVING, LIMIT, and OFFSET UNION ... 

sqlite3_reset()

 ... might still fail and the sqlite3_reset(S) call might return SQLITE_BUSY if locking constraints prevent the database change from committing. Therefore, it is important that applications check the return code from sqlite3_reset(S) even if no prior call to sqlite3_step ... 

 ... It does not mean that the changes are actually committed. The commit does not occur until the statement finishes, and maybe not even then if the statement is part of a larger transaction. Changes to the database are still atomic ... 

 ... There are literally trillions of SQLite database files in circulation and the SQLite developers are committing to supporting those files for decades into the future. Prior to SQLite version 3.0.0 (2004-06-18), the file format did sometimes ... 

sqlite3_stmt_readonly()

 ... Transaction control statements such as BEGIN, COMMIT, ROLLBACK, SAVEPOINT, and RELEASE cause sqlite3_stmt_readonly() to return true, since the statements themselves do not actually modify the database but rather they control the timing of when other statements modify the database. The ... 

4.2. Deferred Foreign Key Constraints  ... However, COMMIT will fail as long as foreign key constraints remain in violation. If the current statement is not inside an explicit transaction (a BEGIN/COMMIT/ROLLBACK block), then an implicit transaction is committed as soon as the statement has ... 

sqlite3_autovacuum_pages()

 ... If there are multiple ATTACH-ed database files that are being modified as part of a transaction commit, then the autovacuum pages callback is invoked separately for each file. The callback is not reentrant. The callback function should not attempt ... 

 ... But if the host computer crashes in the middle of a COMMIT where two or more database files are updated, some of those files might get the changes where others might not. There is a limit, set using sqlite3_limit() and ... 

sqlite3_last_insert_rowid()

 ... As well as being set automatically as rows are inserted into database tables, the value returned by this function may be set explicitly by sqlite3_set_last_insert_rowid() Some virtual table implementations may INSERT rows into rowid tables as part of committing a ...