Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Correct minor typo. |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
9589b9982bf3fab567e0241b4fa19ea4 |
| User & Date: | mistachkin 2013-11-18 20:57:03 |
Context
|
2013-11-18
| ||
| 23:39 | Updates to the "opcode.html" and "sqlite.html" documents. check-in: 45a6eaaaa7 user: drh tags: trunk | |
| 20:57 | Correct minor typo. check-in: 9589b9982b user: mistachkin tags: trunk | |
| 18:48 | Fix documentation typos pointed out on the mailing list by Philip Newton. check-in: b8e6ac4ce4 user: drh tags: trunk | |
Changes
Changes to pages/tempfiles.in.
129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 |
the journal file and instead overwrites the rollback journal header
with zeros, which prevents other processes from rolling back the
journal and thus has the same effect as deleting the journal file, though
without the expense of actually removing the file from disk. In other
words, journal mode PERSIST exhibits the same behavior as is seen
in EXCLUSIVE locking mode. The
OFF journal mode causes SQLite to omit the rollback journal, completely.
In other words, no rollback journal is every written if journal mode is
set to OFF.
The OFF journal mode disables the atomic
commit and rollback capabilities of SQLite. The ROLLBACK command
is not available when OFF journal mode is set. And if a crash or power
loss occurs in the middle of a transaction that uses the OFF journal
mode, no recovery is possible and the database file will likely
go corrupt.
|
| |
129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 |
the journal file and instead overwrites the rollback journal header with zeros, which prevents other processes from rolling back the journal and thus has the same effect as deleting the journal file, though without the expense of actually removing the file from disk. In other words, journal mode PERSIST exhibits the same behavior as is seen in EXCLUSIVE locking mode. The OFF journal mode causes SQLite to omit the rollback journal, completely. In other words, no rollback journal is ever written if journal mode is set to OFF. The OFF journal mode disables the atomic commit and rollback capabilities of SQLite. The ROLLBACK command is not available when OFF journal mode is set. And if a crash or power loss occurs in the middle of a transaction that uses the OFF journal mode, no recovery is possible and the database file will likely go corrupt. |