Documentation Source Text

Check-in [f230c5ce7d]
Login

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

Overview
Comment:Fix typo.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: f230c5ce7ddd1fb673a5c171d612cc86a5fdc1407ebd1086412f52ca657131a6
User & Date: mistachkin 2017-05-02 01:31:11
Context
2017-05-02
18:46
Update the change log and the speed-and-size graph. check-in: 03fde5ae27 user: drh tags: trunk
01:31
Fix typo. check-in: f230c5ce7d user: mistachkin tags: trunk
2017-04-29
18:03
Further improvements to the opcode.html document. check-in: 1f4f0600ef user: drh tags: trunk
Changes
Hide Diffs Unified Diffs Ignore Whitespace Patch

Changes to pages/pragma.in.

1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
       [database header]. 

<p>    ^SQLite automatically increments the schema-version whenever the
       schema changes. ^As each SQL statement runs, the schema version is
       checked to ensure that the schema has not changed since the SQL
       statement was [sqlite3_prepare|prepared].
       ^Subverting this mechanism by using "PRAGMA schema_version"
       my cause SQL statement to run using an obsolete schema,
       which can lead to incorrect answers and/or
       [cfgerrors|database corruption].

       DISCLAIMER

<p>    ^For the purposes of this pragma, the [VACUUM] command is considered
       a schema change, since [VACUUM] will usual alter the "rootpage"







|







1480
1481
1482
1483
1484
1485
1486
1487
1488
1489
1490
1491
1492
1493
1494
       [database header]. 

<p>    ^SQLite automatically increments the schema-version whenever the
       schema changes. ^As each SQL statement runs, the schema version is
       checked to ensure that the schema has not changed since the SQL
       statement was [sqlite3_prepare|prepared].
       ^Subverting this mechanism by using "PRAGMA schema_version"
       may cause SQL statement to run using an obsolete schema,
       which can lead to incorrect answers and/or
       [cfgerrors|database corruption].

       DISCLAIMER

<p>    ^For the purposes of this pragma, the [VACUUM] command is considered
       a schema change, since [VACUUM] will usual alter the "rootpage"