SQLITE_FCNTL_LOCKSTATE, SQLITE_FCNTL_GET_LOCKPROXYFILE, SQLITE_FCNTL_SET_LOCKPROXYFILE, SQLITE_FCNTL_LAST_ERRNO, SQLITE_FCNTL_SIZE_HINT, SQLITE_FCNTL_CHUNK_SIZE ... 

 ... The SQLITE_FCNTL_JOURNAL_POINTER opcode is used to obtain a pointer to the sqlite3_file object associated with the journal file (either the rollback journal or the write-ahead log) for a particular database connection. See also SQLITE_FCNTL_FILE_POINTER. No longer in use. The ... 

 ... When overwriting the original, a rollback journal or write-ahead log WAL file is used just as it would be for any other database transaction. This means that when VACUUMing a database, as much as twice the size of the ... 

6. Result Code Meanings  ... The SQLITE_READONLY_ROLLBACK error code indicates that a database cannot be opened because it has a hot journal that needs to be rolled back but cannot because the database is readonly. (778) SQLITE_IOERR_WRITE The SQLITE_IOERR_WRITE error code is an extended error ... 

8.5. Journal Tests One of the things that SQLite does to ensure that transactions are atomic across system crashes and power failures is to write all changes into the rollback journal file prior to changing the database. The TCL test harness contains an ... 

3. Variety of Error Messages  ... The error code is SQLITE_NOTICE_RECOVER_ROLLBACK when recovering a rollback journal and SQLITE_NOTICE_RECOVER_WAL when recovering a write-ahead log. SQLITE_WARNING messages are logged when database files are renamed or aliased in ways that can lead to database corruption. (See 1 and ... 

sqlite3_backup_init(), sqlite3_backup_step(), sqlite3_backup_finish(), sqlite3_backup_remaining(), sqlite3_backup_pagecount()

 ... The sqlite3_backup_step() might return SQLITE_READONLY if the destination database was opened read-only, or the destination database is using write-ahead-log journaling and the destination and source page sizes differ, or the destination database is an in-memory database ... 

 ... For example, an application that does not care about crash recovery or rollback, might make the open of a journal file a no-op. Writes to this journal are also a no-op. Any attempt to read the journal returns ... 

4. Options To Set Default Parameter Values  ... SQLITE_DEFAULT_JOURNAL_SIZE_LIMIT=<bytes> This option sets the size limit on rollback journal files in persistent journal mode and exclusive locking mode and on the size of the write-ahead log file in WAL mode. When this compile-time option ... 

 ... It also describe how the workings of SQLite, and in particular the journal and WAL, can be used to ascertain what has happened in a manner that cannot be determined from the data alone. The book covers basic SQL queries ... 

sqlite3_open(), sqlite3_open16()

 ... The nolock parameter is a boolean query parameter which if set disables file locking in rollback journal modes. This is useful for accessing a database on a filesystem that does not support locking. Caution: Database corruption might result if two ...