Documentation Source Text

Check-in [be9d86ac89]
Login

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

Overview
Comment:Fix typo.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: be9d86ac89c555c416fb7dcbc56d98787e0cfcdcd68f513878ee498d939d1598
User & Date: mistachkin 2018-09-17 12:48:51.663
Context
2018-09-17
18:38
Initial change log for version 3.25.1. (check-in: 9daac74fb0 user: drh tags: trunk)
12:48
Fix typo. (check-in: be9d86ac89 user: mistachkin tags: trunk)
2018-09-15
04:26
Version 3.25.0 (check-in: 9089e073c4 user: drh tags: trunk, release, version-3.25.0)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/fileio.in.
︙︙
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766

    database files in main-memory on a per-page basis. When SQLite requires
    data from a database file to satisfy a database query, it checks the <i>
    page cache</i> for usable cached versions of the required database
    pages before loading it from the database file. If no usable cache
    entry can be found and the database page data is loaded from the database
    file, it is cached in the <i>page cache</i> in case the same data is 
    needed again later. Because reading from the database file is assumed to
    be an order of magnitude faster than reading from main-memory, caching
    database page content in the <i>page cache</i> to minimize the number
    of read operations performed on the database file is a significant
    performance enhancement.

  <p>
    The <i>page cache</i> is also used to buffer database write operations.
    When SQLite is required to modify one of more of the <i>database pages</i>








|








752
753
754
755
756
757
758
759
760
761
762
763
764
765
766

    database files in main-memory on a per-page basis. When SQLite requires
    data from a database file to satisfy a database query, it checks the <i>
    page cache</i> for usable cached versions of the required database
    pages before loading it from the database file. If no usable cache
    entry can be found and the database page data is loaded from the database
    file, it is cached in the <i>page cache</i> in case the same data is 
    needed again later. Because reading from the database file is assumed to
    be an order of magnitude slower than reading from main-memory, caching
    database page content in the <i>page cache</i> to minimize the number
    of read operations performed on the database file is a significant
    performance enhancement.

  <p>
    The <i>page cache</i> is also used to buffer database write operations.
    When SQLite is required to modify one of more of the <i>database pages</i>
︙︙