Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix typos. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
63898e2980fc31045179879330850a88 |
User & Date: | drh 2015-10-12 18:04:36.539 |
Context
2015-10-12
| ||
18:25 | Update test statistics. (check-in: be7c2233a2 user: drh tags: trunk) | |
18:04 | Fix typos. (check-in: 63898e2980 user: drh tags: trunk) | |
17:05 | Adjust dates in the change log to exactly correspond to the version control check-in dates. (check-in: cc89254370 user: drh tags: trunk) | |
Changes
Changes to pages/amalgamation.in.
︙ | ︙ | |||
59 60 61 62 63 64 65 | is that the additional optimizations often take the form of function inlining which tends to make the size of the resulting binary image larger.</p> <tcl>hd_fragment amal32k {split amalgamation}</tcl> <h2>2.0 The Split Amalgamation</h2> | | | 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 | is that the additional optimizations often take the form of function inlining which tends to make the size of the resulting binary image larger.</p> <tcl>hd_fragment amal32k {split amalgamation}</tcl> <h2>2.0 The Split Amalgamation</h2> <p>Developers sometimes experience trouble debugging the 185,000-line-long amalgamation source file because some debuggers are only able to handle source code line numbers less than 32,768. The amalgamation source code runs fine. One just cannot single-step through it in a debugger. <p>To circumvent this limitation, the amalgamation is also available in a split form, consisting of files "sqlite3-1.c", "sqlite3-2.c", and |
︙ | ︙ |
Changes to pages/dbstat.in.
︙ | ︙ | |||
18 19 20 21 22 23 24 | <blockquote><pre> SELECT * FROM dbstat; </pre></blockquote> <p> If a named virtual table that uses the dbstat module is desired, | | | 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 | <blockquote><pre> SELECT * FROM dbstat; </pre></blockquote> <p> If a named virtual table that uses the dbstat module is desired, then the recommended way to create an instance of the dbstat virtual table is as follows: <blockquote><pre> CREATE VIRTUAL TABLE temp.stat USING dbstat(main); </pre></blockquote> <p> |
︙ | ︙ |
Changes to pages/fts5.in.
︙ | ︙ | |||
172 173 174 175 176 177 178 | <ul> <li> Non-ASCII range characters (i.e. unicode codepoints greater than 127), or <li> One of the 52 upper and lower case ASCII characters, or <li> One of the 10 decimal digit ASCII characters, or <li> The underscore character (unicode codepoint 96). | | | 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 | <ul> <li> Non-ASCII range characters (i.e. unicode codepoints greater than 127), or <li> One of the 52 upper and lower case ASCII characters, or <li> One of the 10 decimal digit ASCII characters, or <li> The underscore character (unicode codepoint 96). <li> The substitute character (unicode codepoint 26). </ul> Strings that include any other characters must be quoted. Characters that are not currently allowed in barewords, are not quote characters and do not currently serve any special purpose in FTS5 query expressions may at some point in the future be allowed in barewords or used to implement new query functionality. This means that queries that are currently |
︙ | ︙ |
Changes to pages/vtab.in.
︙ | ︙ | |||
479 480 481 482 483 484 485 | step HIDDEN ); </pre></blockquote> <p>The [sqlite3_module.xBestIndex] method in the implementation of this table checks for equality constraints against the HIDDEN columns, and uses those as input parameters to determine the range of integer "value" outputs | | | 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 | step HIDDEN ); </pre></blockquote> <p>The [sqlite3_module.xBestIndex] method in the implementation of this table checks for equality constraints against the HIDDEN columns, and uses those as input parameters to determine the range of integer "value" outputs to generate. Reasonable defaults are used for any unconstrained columns. For example, to list all integers between 5 and 50: <blockquote><pre> SELECT value FROM generate_series(5,50); </pre></blockquote> <p>The previous query is equivalent to the following: |
︙ | ︙ |