Documentation Source Text

Check-in [f5137e463c]
Login

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

Overview
Comment:Read-only WAL mode in 3.22, not 3.20.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:f5137e463c3da677d58bd2d84c1c8834ed782039a16f4624958133e3befab383
User & Date: drh 2018-05-22 15:31:38
Context
2018-05-22
15:40
Better phrasing of the read-only WAL mode disadvantage in wal.html. check-in: 729be21bb1 user: drh tags: trunk
15:31
Read-only WAL mode in 3.22, not 3.20. check-in: f5137e463c user: drh tags: trunk
15:28
Update information on read-only WAL-mode databases to conform with the new capabilities added in version 3.22.0. check-in: ba027764e3 user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/wal.in.

319
320
321
322
323
324
325
326
327
328
329
330
331
332
333

<tcl>hd_fragment {readonly} {read-only WAL databases}</tcl>
<h1>Read-Only Databases</h1>

<p>Older versions of SQLite could not read a WAL-mode database that was
read-only.  In other words, write access was required in order ot read a
WAL-mode database.  This constraint was relaxed beginning with
SQLite [version 3.20.0] ([dateof:3.20.0]).

<p>On newer versions of SQLite,
a WAL-mode database on read-only media, or a WAL-mode database that lacks
write permission, can still be read as long as one or more of the following
conditions are met:
<ol>
<li>The <tt>-shm</tt> and <tt>-wal</tt> files already exists and are readable







|







319
320
321
322
323
324
325
326
327
328
329
330
331
332
333

<tcl>hd_fragment {readonly} {read-only WAL databases}</tcl>
<h1>Read-Only Databases</h1>

<p>Older versions of SQLite could not read a WAL-mode database that was
read-only.  In other words, write access was required in order ot read a
WAL-mode database.  This constraint was relaxed beginning with
SQLite [version 3.22.0] ([dateof:3.22.0]).

<p>On newer versions of SQLite,
a WAL-mode database on read-only media, or a WAL-mode database that lacks
write permission, can still be read as long as one or more of the following
conditions are met:
<ol>
<li>The <tt>-shm</tt> and <tt>-wal</tt> files already exists and are readable