Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Another typo in howtocorrupt.html |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
0a0f9e093bd3d1b3382fb1759ae1aa94 |
| User & Date: | drh 2011-04-12 19:40:58 |
Context
|
2011-04-13
| ||
| 18:37 | Update documentation for the 3.7.6.1 patch release. Fix a typos in the FTS4 documentation. (check-in: 0a742ee49a user: drh tags: trunk) | |
|
2011-04-12
| ||
| 19:40 | Another typo in howtocorrupt.html (check-in: 0a0f9e093b user: drh tags: trunk) | |
| 19:31 | Fix typos in the howtocorrupt.html document. (check-in: ee071c325f user: drh tags: trunk) | |
Changes
Changes to pages/howtocorrupt.in.
316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 |
Version 3.7.0 was simply begin overly zealous in its corruption detection.</p> <p>The problem was fixed on 2011-02-20. The fix first appears in SQLite version 3.7.6.</p> <h3>7.2 Corruption follow switches between rollback and WAL modes</h3> <p>Repeatedly switch an SQLite database in and out of [WAL | 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 that the database has changed. That second process 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 |
| |
316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 |
Version 3.7.0 was simply begin overly zealous in its corruption detection.</p>
<p>The problem was fixed on 2011-02-20. The fix first appears in
SQLite version 3.7.6.</p>
<h3>7.2 Corruption follow switches between rollback and WAL modes</h3>
<p>Repeatedly switching an SQLite database in and out of [WAL | 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 that the database has changed. That second process
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
|