Documentation Source Text

Check-in [556fe1bb34]
Login

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

Overview
Comment:Fix a typo on the pragma documentation.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 556fe1bb348bf3cc13e99da866cb8e15358edf9e
User & Date: drh 2013-03-03 00:19:41.932
Context
2013-03-09
15:02
Update change log and index for the 3-way join/affinity bug. (check-in: b7385b0ef3 user: drh tags: trunk)
2013-03-03
00:19
Fix a typo on the pragma documentation. (check-in: 556fe1bb34 user: drh tags: trunk)
2013-03-02
17:37
Add a backwards compatibility note on the documentation of cache_size and its behavior when N is negative. (check-in: 92f6694092 user: drh tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/pragma.in.
︙︙
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593

    held. ^The first time the database is written, an exclusive lock is
    obtained and held.</p>

    <p>^Database locks obtained by a connection in EXCLUSIVE mode may be
    released either by closing the database connection, or by setting the
    locking-mode back to NORMAL using this pragma and then accessing the
    database file (for read or write). ^Simply setting the locking-mode to
    NORMAL is not enough - locks are not be released until the next time
    the database file is accessed.</p>

    <p>There are three reasons to set the locking-mode to EXCLUSIVE.
    <ol>
    <li>^The application wants to prevent other processes from
        accessing the database file.
    <li>^The number of system calls for filesystem operations is reduced,








|








579
580
581
582
583
584
585
586
587
588
589
590
591
592
593

    held. ^The first time the database is written, an exclusive lock is
    obtained and held.</p>

    <p>^Database locks obtained by a connection in EXCLUSIVE mode may be
    released either by closing the database connection, or by setting the
    locking-mode back to NORMAL using this pragma and then accessing the
    database file (for read or write). ^Simply setting the locking-mode to
    NORMAL is not enough - locks are not released until the next time
    the database file is accessed.</p>

    <p>There are three reasons to set the locking-mode to EXCLUSIVE.
    <ol>
    <li>^The application wants to prevent other processes from
        accessing the database file.
    <li>^The number of system calls for filesystem operations is reduced,
︙︙