/ Check-in [99a7bd83]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Fix typo in the locking document. (CVS 1576)
Downloads: Tarball | ZIP archive | SQL archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1:99a7bd83ac38e14bb936a834634313cf98279a62
User & Date: drh 2004-06-12 14:11:38
Context
2004-06-12
18:12
Improve the speed of OP_Column through better caching. (CVS 1577) check-in: f687977a user: drh tags: trunk
14:11
Fix typo in the locking document. (CVS 1576) check-in: 99a7bd83 user: drh tags: trunk
09:25
(1) Modifications to the user-function interface and (2) Internal changes to automatically created indices. (CVS 1575) check-in: 5903f538 user: danielk1977 tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to www/lockingv3.tcl.

462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
unspecified reasons.  The author cannot verify any of these reports.
But if they are true, it means that database corruption is a possibility
following an unexpected power loss.  These are hardware and/or operating
system bugs that SQLite is unable to defend against.
</p>

<p>
If a crash or power failure occurs and results in a hot journal, but that
journal is deleted.  The next process to open the database will not
know that it contains changes that need to be rolled back.  The rollback
will not occur and the database will be left in an inconsistent state.
Rollback journals might be deleted for any number of reasons:
</p>

<ul>
<li>An administrator might be cleaning up after an OS crash or power failure,







|
|







462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
unspecified reasons.  The author cannot verify any of these reports.
But if they are true, it means that database corruption is a possibility
following an unexpected power loss.  These are hardware and/or operating
system bugs that SQLite is unable to defend against.
</p>

<p>
If a crash or power failure occurs and results in a hot journal but that
journal is deleted, the next process to open the database will not
know that it contains changes that need to be rolled back.  The rollback
will not occur and the database will be left in an inconsistent state.
Rollback journals might be deleted for any number of reasons:
</p>

<ul>
<li>An administrator might be cleaning up after an OS crash or power failure,