Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Fix another howtocorrupt.html typo.|
|Timelines:||family | ancestors | descendants | both | branch-3.22|
|Files:||files | file ages | folders|
|User & Date:||drh 2018-01-31 02:53:43|
|14:43||Fix a typo in the flattening rules of the optoverview.html document. check-in: 20ecb45b42 user: drh tags: branch-3.22|
|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|
Changes to pages/howtocorrupt.in.
528 528 of recovery because the previous process writing to it crashed in the 529 529 middle of a transaction and two or more processes try to open the 530 530 that database at the same time, then the race condition might cause 531 531 one of those processes to get a false indication that the recovery 532 532 has already completed, allowing that process to continue using the 533 533 database file without running recovery first. If that process writes 534 534 to the file, then the file might go corrupt. This race condition 535 -had apparently existing in all prior versions of SQLite for Windows going 535 +had apparently existed in all prior versions of SQLite for Windows going 536 536 back to 2004. But the race was very tight. Practically speaking, you 537 537 need a fast multi-core machine in which you launch two processes to run 538 538 recovery at the same moment on two separate cores. This defect was 539 539 on Windows systems only and did not affect the posix OS interface.</p>