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

sqlite3_last_insert_rowid()

 ... set explicitly by sqlite3_set_last_insert_rowid() Some virtual table implementations may INSERT rows into rowid tables as part of committing a transaction (e.g. to flush data accumulated in memory to disk). In this case subsequent calls to this function return the ... 

 ... Start a transaction. Remember the format of all indexes, triggers, and views associated with table X. This information will be needed in step 8 below. One way to do this is to run a query like the following: SELECT type ... 

 ... If you have a multi-statement transaction and within that transaction an UPDATE or INSERT statement fails due to a constraint, then you try to rollback the whole transaction, the rollback might not work correctly. See Ticket #1171 for details ... 

 ... In WAL mode, each transaction had to be padded out to the next 4096-byte boundary in the WAL file, rather than the next 512-byte boundary, resulting in thousands of extra bytes being written per transaction. The extra write ... 

sqlite3_blob_open()

 ... Such changes will eventually commit if the transaction continues to completion. Use the sqlite3_blob_bytes() interface to determine the size of the opened blob. The size of a blob may not be changed by this interface. Use the UPDATE SQL command ... 

 ... REINDEX RELEASE RENAME REPLACE RESTRICT RETURNING RIGHT ROLLBACK ROW ROWS SAVEPOINT SELECT SET TABLE TEMP TEMPORARY THEN TIES TO TRANSACTION TRIGGER UNBOUNDED UNION UNIQUE UPDATE USING VACUUM VALUES VIEW VIRTUAL WHEN WHERE WINDOW WITH WITHOUT This page last modified on ... 

2.2. Instruction Format  ... If the execution stopped due to an error, any pending transactions are terminated and changes made to the database are rolled back. The ResultRow opcode causes the bytecode engine to pause and the corresponding sqlite3_step() call to return SQLITE_ROW. Before ... 

 ... Simplified Application Development Single-File Documents High-Level Query Language Accessible Content Cross-Platform Atomic Transactions Incremental And Continuous Updates Easily Extensible Performance Concurrent Use By Multiple Processes Multiple Programming Languages Better Applications Each of these points will be described ... 

 ... It presents step-by-step examples to create schema, execute transactions and access data from Android, BlackBerry and iOS applications. In addition, it presents ADB Shell and SQLite command-line shell from ADB Shell to access the SQLite Database created ...