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