Documentation Source Text

Check-in [4bfef7edb7]
Login

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

Overview
Comment:Fix typos in the cache_spill pragma documentation.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 4bfef7edb7fa904e0184913e04a17c579863e9b4
User & Date: drh 2013-08-20 17:06:48.724
Context
2013-08-23
01:57
Add documentation for the query_only and defer_foreign_keys pragmas. Update the change log for the 3.8.0 release. (check-in: 8e16497ef1 user: drh tags: trunk)
2013-08-20
17:06
Fix typos in the cache_spill pragma documentation. (check-in: 4bfef7edb7 user: drh tags: trunk)
2013-08-19
14:26
Fix a typo in the RTREE documentation. (check-in: 9ceaba9f7f user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/pragma.in.
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
    bindings that do not provide direct access to [sqlite3_busy_timeout()].
}

Pragma cache_spill {
    <p>^(<b>PRAGMA cache_spill;
         <br>PRAGMA cache_spill=</b><i>boolean</i><b>;</b>)^</p>

    <p>^(The cache_spill pragme enables or disables the ability of the pager
    to spill dirty cache pages to the database file in the middle of a 
    transaction.)^  ^(Cache_spill is enabled by default)^ and most applications
    should leave it that way as cache spilling is unusally advantageous.
    However, a cache spill has the side-effect of acquiring an
    [EXCLUSIVE lock] on the database file.  Hence, some applications that
    have large long-running transactions may want to disable cache spilling
    in order to prevent the application from acquiring an exclusive lock
    on the database until the moment that the transaction [COMMIT]s.
}








|


|







213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
    bindings that do not provide direct access to [sqlite3_busy_timeout()].
}

Pragma cache_spill {
    <p>^(<b>PRAGMA cache_spill;
         <br>PRAGMA cache_spill=</b><i>boolean</i><b>;</b>)^</p>

    <p>^(The cache_spill pragma enables or disables the ability of the pager
    to spill dirty cache pages to the database file in the middle of a 
    transaction.)^  ^(Cache_spill is enabled by default)^ and most applications
    should leave it that way as cache spilling is usually advantageous.
    However, a cache spill has the side-effect of acquiring an
    [EXCLUSIVE lock] on the database file.  Hence, some applications that
    have large long-running transactions may want to disable cache spilling
    in order to prevent the application from acquiring an exclusive lock
    on the database until the moment that the transaction [COMMIT]s.
}