Small. Fast. Reliable.
Choose any three.
Choose any three.
|
C API: Recover snapshots from a wal file
(c3ref/snapshot_recover.html)
sqlite3_snapshot_recover()
... It is an error if there is already a read
transaction open on the database, or if the database is not a WAL mode
database.
SQLITE_OK is returned if successful, or an SQLite error code otherwise.
This interface is only ...
|
|
Using SQLite In Multi-Threaded Applications
(threadsafe.html)
4. Run-time selection of threading mode
... The
SQLITE_OPEN_NOMUTEX flag causes the database connection to be in the
multi-thread mode and the SQLITE_OPEN_FULLMUTEX flag causes the connection
to be in serialized mode. If neither flag is specified or if
sqlite3_open() or sqlite3_open16() are used instead of ...
|
|
Uniform Resource Identifiers
(uri.html)
3.3. Recognized Query Parameters
... mode=romode=rwmode=rwcmode=memory
The mode query parameter determines if the new database is opened
read-only, read-write, read-write and created if it does not exist, or
that the database is a pure in-memory database that ...
|
|
C API: Standard File Control Opcodes
(c3ref/c_fcntl_begin_atomic_write.html)
SQLITE_FCNTL_LOCKSTATE, SQLITE_FCNTL_GET_LOCKPROXYFILE, SQLITE_FCNTL_SET_LOCKPROXYFILE, SQLITE_FCNTL_LAST_ERRNO, SQLITE_FCNTL_SIZE_HINT, SQLITE_FCNTL_CHUNK_SIZE ...
... If the integer is -1, then it is overwritten with the current
zero-damage mode setting.
The SQLITE_FCNTL_OVERWRITE opcode is invoked by SQLite after opening
a write transaction to indicate that, unless it is rolled back for some
reason, the ...
|
|
VACUUM
(lang_vacuum.html)
... 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 ...
|
|
How To Corrupt An SQLite Database File
(howtocorrupt.html)
8.2. Corruption following switches between rollback and WAL modes
Repeatedly switching an SQLite database in and out of WAL mode
and running the VACUUM command in between switches, in one process or
thread, can cause another process or thread that has the database file
open to miss the fact ...
|
|
Temporary Files Used By SQLite
(tempfiles.html)
2.2. Write-Ahead Log (WAL) Files
A write-ahead log or WAL file is used in place of a rollback journal
when SQLite is operating in WAL mode. As with the rollback journal,
the purpose of the WAL file is to implement atomic commit and rollback ...
|
|
Result and Error Codes
(rescode.html)
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 ...
|
|
WAL-mode File Format
(walformat.html)
1.5. Variations
When PRAGMA locking_mode=EXCLUSIVE (exclusive locking mode) is set,
only a single client is allowed to have the database open at one time. Since
only a single client can use the database, the shm file is omitted.
The single client ...
|
|
Isolation In SQLite
(isolation.html)
... There are two major "journal modes".
The older "rollback mode" corresponds to using the "DELETE", "PERSIST",
or "TRUNCATE" options to the journal_mode pragma. In rollback mode,
changes are written directly into the database file, while simultaneously
a separate rollback journal ...
|
Page generated by FTS5 in about 84.27 ms.