Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Merge fixes from the 3.20 branch. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA3-256: |
de8b5d698b40eb4b458487e509652ce7 |
User & Date: | drh 2019-09-27 11:30:51.689 |
Context
2019-09-27
| ||
17:55 | Updates so that documentation agrees with requirement marks. (check-in: f1a1831162 user: drh tags: trunk) | |
11:30 | Merge fixes from the 3.20 branch. (check-in: de8b5d698b user: drh tags: trunk) | |
11:30 | Type fixes (check-in: 003eb4df17 user: drh tags: trunk) | |
2019-09-24
| ||
10:30 | Use single-quoted strings in the documention for PRAGMA encoding. (check-in: 4c6aa056b7 user: drh tags: branch-3.29) | |
Changes
Changes to pages/lang.in.
︙ | ︙ | |||
741 742 743 744 745 746 747 | not a transaction started by BEGIN) is committed automatically when the last active statement finishes. A statement finishes when its last cursor closes, which is guaranteed to happen when the prepared statement is [sqlite3_reset() | reset] or [sqlite3_finalize() | finalized]. Some statements might "finish" for the purpose of transaction control prior to being reset or finalized, but there is no guarantee of this. The only way to ensure that a | | | 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 | not a transaction started by BEGIN) is committed automatically when the last active statement finishes. A statement finishes when its last cursor closes, which is guaranteed to happen when the prepared statement is [sqlite3_reset() | reset] or [sqlite3_finalize() | finalized]. Some statements might "finish" for the purpose of transaction control prior to being reset or finalized, but there is no guarantee of this. The only way to ensure that a statement has "finished" is to invoke [sqlite3_reset()] or [sqlite3_finalize()] on that statement. An open [sqlite3_blob] used for incremental BLOB I/O also counts as an unfinished statement. The [sqlite3_blob] finishes when it is [sqlite3_blob_close() | closed]. </p> <p> ^The explicit COMMIT command runs immediately, even if there are |
︙ | ︙ |
Changes to pages/pragma.in.
︙ | ︙ | |||
563 564 565 566 567 568 569 | DISCLAIMER } Pragma encoding { <p>^(<b>PRAGMA encoding; | | | | | | | | | 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 | DISCLAIMER } Pragma encoding { <p>^(<b>PRAGMA encoding; <br>PRAGMA encoding = 'UTF-8'; <br>PRAGMA encoding = 'UTF-16'; <br>PRAGMA encoding = 'UTF-16le'; <br>PRAGMA encoding = 'UTF-16be';</b>)^</p> <p>^In first form, if the main database has already been created, then this pragma returns the text encoding used by the main database, one of 'UTF-8', 'UTF-16le' (little-endian UTF-16 encoding) or 'UTF-16be' (big-endian UTF-16 encoding). ^If the main database has not already been created, then the value returned is the text encoding that will be used to create the main database, if it is created by this session.</p> <p>^The second through fifth forms of this pragma set the encoding that the main database will be created with if it is created by this session. ^The string 'UTF-16' is interpreted as "UTF-16 encoding using native machine byte-ordering". ^It is not possible to change the text encoding of a database after it has been created and any attempt to do so will be silently ignored.</p> <p>^Once an encoding has been set for a database, it cannot be changed.</p> <p>^Databases created by the [ATTACH] command always use the same encoding |
︙ | ︙ |