Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Typo in the how-to-corrupt document. |
|---|---|
| Timelines: | family | ancestors | descendants | both | branch-3.22 |
| Files: | files | file ages | folders |
| SHA3-256: | 6ad1abb44867c2ca7d5572e548941e6b |
| User & Date: | drh 2018-01-31 02:52:09 |
Context
|
2018-01-31
| ||
| 02:53 | Fix another howtocorrupt.html typo. check-in: 633d838aa0 user: drh tags: branch-3.22 | |
| 02:52 | Typo in the how-to-corrupt document. check-in: 6ad1abb448 user: drh tags: branch-3.22 | |
|
2018-01-26
| ||
| 15:50 | Turn on "fancy-format" for the optoverview.html document. check-in: 98e66068fe user: drh tags: trunk | |
Changes
Changes to pages/howtocorrupt.in.
471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 |
or thread might then try to modify the database using a stale cache and cause database corruption.</p> <p>This problem was discovered during internal testing and has never been observed in the wild. The problem was fixed on 2011-01-27 and in version 3.7.5.</p> <h2> I/O while obtaining a lock leads to corruption</h2> <p>If the operating system returns an I/O error while attempting to obtain a certain lock on shared memory in [WAL | WAL mode] then SQLite might fail to reset its cache, which could lead to database corruption if subsequent writes are attempted.</p> <p>Note that this problem only occurs if the attempt to acquire the lock |
| |
471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 |
or thread might then try to modify the database using a stale cache and
cause database corruption.</p>
<p>This problem was discovered during internal testing and has never been
observed in the wild. The problem was fixed on 2011-01-27 and in version
3.7.5.</p>
<h2> I/O error while obtaining a lock leads to corruption</h2>
<p>If the operating system returns an I/O error while attempting to obtain
a certain lock on shared memory in [WAL | WAL mode] then SQLite might fail
to reset its cache,
which could lead to database corruption if subsequent writes are attempted.</p>
<p>Note that this problem only occurs if the attempt to acquire the lock
|