Documentation Source Text

Check-in [0b012929c4]
Login

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

Overview
Comment:Fix a typo in the isolation.html document.
Timelines: family | ancestors | descendants | both | branch-3.8.8
Files: files | file ages | folders
SHA1: 0b012929c481b2340aab3c11c8a71810b2d25868
User & Date: drh 2015-03-16 18:07:54
Context
2015-03-16
20:37
Fix a typo in the queryplanner.html document. check-in: 94ffc3e5cb user: drh tags: branch-3.8.8
18:07
Fix a typo in the isolation.html document. check-in: 0b012929c4 user: drh tags: branch-3.8.8
2015-03-09
19:42
Fix a typo in the tempfiles.html page. check-in: 3f2102936f user: drh tags: branch-3.8.8
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/isolation.in.

91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
is flushed to disk and while all changes are still held in the writer's
private memory space.  But before any changes are made to the database file
on disk, all readers must be (temporally) expelled in order to give the writer
exclusive access to the database file.  
Hence, readers are prohibited from seeing incomplete
transactions by virtue of being locked out of the database while the
transaction is being written to disk.  Only after the transaction is
complete written and synced to disk and commits are the readers allowed
back into the database.  Hence readers never get a chance to see partially
written changes.
</p>

<p>
WAL mode permits simultaneous readers and writers.  It can do this because
changes do not overwrite the original database file, but rather go







|







91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
is flushed to disk and while all changes are still held in the writer's
private memory space.  But before any changes are made to the database file
on disk, all readers must be (temporally) expelled in order to give the writer
exclusive access to the database file.  
Hence, readers are prohibited from seeing incomplete
transactions by virtue of being locked out of the database while the
transaction is being written to disk.  Only after the transaction is
completely written and synced to disk and commits are the readers allowed
back into the database.  Hence readers never get a chance to see partially
written changes.
</p>

<p>
WAL mode permits simultaneous readers and writers.  It can do this because
changes do not overwrite the original database file, but rather go