sqlite3_database_file_object()

If X is the name of a rollback or WAL-mode journal file that is passed into the xOpen method of sqlite3_vfs, then sqlite3_database_file_object(X) returns a pointer to the sqlite3_file object that represents the main database file. This routine ... 

 ... Then we check each of those file journals. If any of the file journals named in the super-journal exists and points back to the super-journal, then the super-journal is not stale. If all file journals are either ... 

5.3. Updating Rollback Journal Headers The next step is to record the full pathname of the super-journal file in the header of every rollback journal. Space to hold the super-journal filename was reserved at the beginning of each rollback journal as the rollback ... 

2.1. Rollback Journals A rollback journal is a temporary file used to implement atomic commit and rollback capabilities in SQLite. (For a detailed discussion of how this works, see the separate document titled Atomic Commit In SQLite.) The rollback journal is always located ... 

sqlite3_filename_database(), sqlite3_filename_journal(), sqlite3_filename_wal()

These routines are available to custom VFS implementations for translating filenames between the main database file, the journal file, and the WAL file. If F is the name of an sqlite database file, journal file, or WAL file passed by ... 

 ... For example, if the original database is call "app.db" then the rollback journal will be called "app.db-journal" and the write-ahead log will be called "app.db-wal". This approach to auxiliary file naming works great on ... 

1.4. Mispairing database files and hot journals  ... Swapping journal files between two different databases. Overwritting a journal file with a different journal file. Moving a journal file from one database to another. Copying a database file without also copying its journal. Overwriting a database file with another ... 

2. How WAL Works The traditional rollback journal works by writing a copy of the original unchanged database content into a separate rollback journal file and then writing changes directly into the database file. In the event of a crash or ROLLBACK, the original ... 

PRAGMA journal_mode PRAGMA schema.journal_mode; PRAGMA schema.journal_mode = DELETE | TRUNCATE | PERSIST | MEMORY | WAL | OFF This pragma queries or sets the journal mode for databases associated with the current database connection. The first form of this pragma queries the current journaling mode for ... 

1.1. Hot Journals If the application or host computer crashes before the transaction completes, then the rollback journal or write-ahead log contains information needed to restore the main database file to a consistent state. When a rollback journal or write-ahead log ...