Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Use single-quoted strings in the documention for PRAGMA encoding. |
|---|---|
| Timelines: | family | ancestors | descendants | both | branch-3.29 |
| Files: | files | file ages | folders |
| SHA3-256: |
4c6aa056b7913a34783be888cb23d673 |
| User & Date: | drh 2019-09-24 10:30:08 |
Context
|
2019-10-02
| ||
| 11:36 | Add the ability to put an ad unit at the top of the index page and the download page. If the file "adunit.txt" exists in the build directory, then the content of that file is copied into the appropriate spot on those two pages. Leaf check-in: ea232463fc user: drh tags: branch-3.29 | |
|
2019-09-27
| ||
| 11:30 | Merge fixes from the 3.20 branch. check-in: de8b5d698b 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 | |
|
2019-09-20
| ||
| 17:37 | Fix a minor typo in the transaction documentation. check-in: 83b8745219 user: drh tags: branch-3.29 | |
Changes
Changes to pages/pragma.in.
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
|
| | | | | | | |
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
|