Small. Fast. Reliable.
Choose any three.
Choose any three.
|
SQLite Changes From Version 3.4.2 To 3.5.0
(34to35.html)
... Potential uses for xFileControl() might be
functions to enable blocking locks with timeouts, to change the
locking strategy (for example to use dot-file locks), to inquire
about the status of a lock, or to break stale locks. The SQLite ...
|
|
Result and Error Codes
(rescode.html)
4. Primary Result Code List
... 16)
SQLITE_ERROR (1)
SQLITE_FORMAT (24)
SQLITE_FULL (13)
SQLITE_INTERNAL (2)
SQLITE_INTERRUPT (9)
SQLITE_IOERR (10)
SQLITE_LOCKED (6)
SQLITE_MISMATCH (20)
SQLITE_MISUSE (21)
SQLITE_NOLFS (22)
SQLITE_NOMEM (7)
SQLITE_NOTADB (26)
SQLITE_NOTFOUND (12 ...
|
|
The C language interface to SQLite Version 2
(c_interface.html)
... SQLITE_LOCKED
This return code is similar to SQLITE_BUSY in that it indicates
that the database is locked. But the source of the lock is a recursive
call to sqlite_exec. This return can only occur if you attempt
to invoke sqlite_exec ...
|
|
Write-Ahead Logging
(wal.html)
8. Use of WAL Without Shared-Memory
... In that case, the database connection remains in EXCLUSIVE mode
as long as the journal mode is WAL; attempts to change the locking
mode using "PRAGMA locking_mode=NORMAL;" are no-ops.
The only way to change out of EXCLUSIVE locking ...
|
|
SQLite Version 3 Overview
(version3.html)
... The
writer must still obtain an exclusive lock on the database for a brief
interval in order to commit its changes, but the exclusive lock is no
longer required for the entire write operation.
A more detailed report on the ...
|
|
C API: Reset A Prepared Statement Object
(c3ref/reset.html)
sqlite3_reset()
... might return SQLITE_ROW but
the overall statement 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 ...
|
|
C API: Write-Ahead Log Commit Hook
(c3ref/wal_hook.html)
sqlite3_wal_hook()
... The callback is invoked by SQLite after the commit has taken place and
the associated write-lock on the database released, so the implementation
may read, write or checkpoint the database as required.
The first parameter passed to the callback ...
|
|
Pragma statements supported by SQLite
(pragma.html)
PRAGMA locking_mode
PRAGMA schema.locking_mode;
PRAGMA schema.locking_mode
= NORMAL | EXCLUSIVE
This pragma sets or queries the database connection locking-mode.
The locking-mode is either NORMAL or EXCLUSIVE.
In NORMAL locking-mode (the default unless overridden at compile-time
using SQLITE_DEFAULT_LOCKING_MODE), a ...
|
|
SQLite Over a Network, Caveats and Considerations
(useovernet.html)
... A similar hazard arises with file locking in network filesystems.
SQLite relies on exclusive locks for write operations, and those have
been known to operate incorrectly for some network filesystems. This
has led to database corruption. That may happen again ...
|
|
C API: Opening A New Database Connection
(c3ref/open.html)
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 ...
|
Page generated by FTS5 in about 81.88 ms.