Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix typo in documentation on EXCLUSIVE locking mode for WAL. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
64593a771c893eb123a8a684357b2514 |
| User & Date: | drh 2012-11-14 12:46:58 |
Context
|
2012-11-26
| ||
| 15:25 | First draft of documentation for the spellfix1 virtual table. (check-in: 3a79eaa3ec user: drh tags: trunk) | |
|
2012-11-14
| ||
| 12:46 | Fix typo in documentation on EXCLUSIVE locking mode for WAL. (check-in: 64593a771c user: drh tags: trunk) | |
|
2012-11-10
| ||
| 14:43 | althttpd.c changes: Send a 403 response to unauthorized agents. Add Ezoom to the list of unauthorized agents. Do not log timeouts if the first line of the HTTP request was never received. (check-in: d61bcab9f4 user: drh tags: trunk) | |
Changes
Changes to pages/wal.in.
396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 |
<p>^If NORMAL locking mode is in effect for the first WAL-mode database access, then the shared-memory wal-index is created. ^This means that the underlying VFS must support the "version 2" shared-memory. ^If the VFS does not support shared-memory methods, then the attempt to open a database that is already in WAL mode, or the attempt convert a database into WAL mode, will fail. ^As long a connection is using a shared-memory wal-index, the locking mode can be changed freely between NORMAL and EXCLUSIVE. ^It is only when the shared-memory wal-index is omitted, when the locking mode is EXCLUSIVE prior to the first WAL-mode database access, that the locking mode is stuck in EXCLUSIVE.</p> <tcl>hd_fragment bkwrds {WAL backwards compatibility}</tcl> <h2>Backwards Compatibility</h2> <p>The database file format is unchanged for WAL mode. However, the WAL file and the [wal-index] are new concepts and so older versions of SQLite will not know |
| | | | | |
396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 |
<p>^If NORMAL locking mode is in effect for the first WAL-mode database access, then the shared-memory wal-index is created. ^This means that the underlying VFS must support the "version 2" shared-memory. ^If the VFS does not support shared-memory methods, then the attempt to open a database that is already in WAL mode, or the attempt convert a database into WAL mode, will fail. ^As long as exactly one connection is using a shared-memory wal-index, the locking mode can be changed freely between NORMAL and EXCLUSIVE. ^It is only when the shared-memory wal-index is omitted, when the locking mode is EXCLUSIVE prior to the first WAL-mode database access, that the locking mode is stuck in EXCLUSIVE.</p> <tcl>hd_fragment bkwrds {WAL backwards compatibility}</tcl> <h2>Backwards Compatibility</h2> <p>The database file format is unchanged for WAL mode. However, the WAL file and the [wal-index] are new concepts and so older versions of SQLite will not know |