Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| SHA1 Hash: | 5d8312cd941b5968a346850991726e0658c4c99b |
|---|---|
| Date: | 2012-12-11 19:11:18 |
| User: | drh |
| Comment: | Documentation typos fixed. |
Tags And Properties
- branch=trunk inherited from [b2e03e19ab]
- sym-trunk inherited from [b2e03e19ab]
Changes
Changes to pages/compile.in
326 326 327 <tcl> 327 <tcl> 328 COMPILE_OPTION {SQLITE_ALLOW_COVERING_INDEX_SCAN=<i><0 or 1></i>} { 328 COMPILE_OPTION {SQLITE_ALLOW_COVERING_INDEX_SCAN=<i><0 or 1></i>} { 329 This C-preprocess macro determines the default setting of the 329 This C-preprocess macro determines the default setting of the 330 [SQLITE_CONFIG_COVERING_INDEX_SCAN] configuration setting. It defaults 330 [SQLITE_CONFIG_COVERING_INDEX_SCAN] configuration setting. It defaults 331 to 1 (on) which means that covering indices are used for full table 331 to 1 (on) which means that covering indices are used for full table 332 scans where possible, in order to reduce I/O and improve performance. 332 scans where possible, in order to reduce I/O and improve performance. 333 However, the use of a covering indice for a full scan will cause results | 333 However, the use of a covering index for a full scan will cause results 334 to appear in a different order from legacy, which could cause some 334 to appear in a different order from legacy, which could cause some 335 (incorrectly-coded) legacy applications to break. Hence, the covering 335 (incorrectly-coded) legacy applications to break. Hence, the covering 336 index scan option can be disabled at compile-time on systems that what 336 index scan option can be disabled at compile-time on systems that what 337 to minimize their risk of exposing errors in legacy applications. 337 to minimize their risk of exposing errors in legacy applications. 338 } 338 } 339 339 340 COMPILE_OPTION {SQLITE_ENABLE_8_3_NAMES=<i><1 or 2></i>} { 340 COMPILE_OPTION {SQLITE_ENABLE_8_3_NAMES=<i><1 or 2></i>} {
Changes to pages/fts3.in
1597 SELECT * FROM t3 WHERE t3 MATCH 'k'; 1597 SELECT * FROM t3 WHERE t3 MATCH 'k'; 1598 </codeblock> 1598 </codeblock> 1599 1599 1600 <p> 1600 <p> 1601 When a row is deleted from an external content FTS4 table, FTS4 needs to 1601 When a row is deleted from an external content FTS4 table, FTS4 needs to 1602 retrieve the column values of the row being deleted from the content table. 1602 retrieve the column values of the row being deleted from the content table. 1603 This is so that FTS4 can update the full-text index entries for each token 1603 This is so that FTS4 can update the full-text index entries for each token 1604 that occurs within the deleted row to indicate that that row has been | 1604 that occurs within the deleted row to indicate that row has been 1605 deleted. If the content table row cannot be found, or if it contains values 1605 deleted. If the content table row cannot be found, or if it contains values 1606 inconsistent with the contents of the FTS index, the results can be difficult 1606 inconsistent with the contents of the FTS index, the results can be difficult 1607 to predict. The FTS index may be left containing entries corresponding to the 1607 to predict. The FTS index may be left containing entries corresponding to the 1608 deleted row, which can lead to seemingly nonsensical results being returned 1608 deleted row, which can lead to seemingly nonsensical results being returned 1609 by subsequent SELECT queries. The same applies when a row is updated, as 1609 by subsequent SELECT queries. The same applies when a row is updated, as 1610 internally an UPDATE is the same as a DELETE followed by an INSERT. 1610 internally an UPDATE is the same as a DELETE followed by an INSERT. 1611 1611
Changes to pages/lang.in
2079 2079 2080 funcdef {instr(X,Y)} {} { 2080 funcdef {instr(X,Y)} {} { 2081 ^The instr(X,Y) function finds the first occurrence of string X within 2081 ^The instr(X,Y) function finds the first occurrence of string X within 2082 string Y and returns the number of prior characters plus 1, or 0 if 2082 string Y and returns the number of prior characters plus 1, or 0 if 2083 X is nowhere found within Y. 2083 X is nowhere found within Y. 2084 ^Or, if X and Y are both BLOBs, then instr(X,Y) returns one 2084 ^Or, if X and Y are both BLOBs, then instr(X,Y) returns one 2085 more than the number bytes prior to the first occurrence of X, or 0 if 2085 more than the number bytes prior to the first occurrence of X, or 0 if 2086 X does not occcur anywhere within Y. | 2086 X does not occur anywhere within Y. 2087 ^If both arguments X and Y to instr(X,Y) are non-NULL and are not BLOBs 2087 ^If both arguments X and Y to instr(X,Y) are non-NULL and are not BLOBs 2088 then both are interpreted as strings. 2088 then both are interpreted as strings. 2089 ^If either X or Y are NULL in instr(X,Y) then the result is NULL. 2089 ^If either X or Y are NULL in instr(X,Y) then the result is NULL. 2090 } 2090 } 2091 2091 2092 funcdef {hex(X)} {} { 2092 funcdef {hex(X)} {} { 2093 ^The hex() function interprets its argument as a BLOB and returns 2093 ^The hex() function interprets its argument as a BLOB and returns
Changes to pages/news.in
57 } 57 } 58 58 59 newsitem {2012-Oct-04} {Release 3.7.14.1} { 59 newsitem {2012-Oct-04} {Release 3.7.14.1} { 60 SQLite [version 3.7.14.1] is a patch release. Changes from the baseline 60 SQLite [version 3.7.14.1] is a patch release. Changes from the baseline 61 version 3.7.14 are minimal and are restricted to fixing three bugs. 61 version 3.7.14 are minimal and are restricted to fixing three bugs. 62 62 63 One of the fixed bugs is a long-standing issue with the TCL interface. 63 One of the fixed bugs is a long-standing issue with the TCL interface. 64 Another is a external compiler bug that SQLite merely works around and | 64 Another is an external compiler bug that SQLite merely works around and 65 that only comes up if you are using the VisualStudio-2012 compiler to 65 that only comes up if you are using the VisualStudio-2012 compiler to 66 generate WinRT applications on ARM with optimizations enabled. The 66 generate WinRT applications on ARM with optimizations enabled. The 67 third problem is an SQLite core bug, introduced in version 3.7.14, that 67 third problem is an SQLite core bug, introduced in version 3.7.14, that 68 can cause a segfault if a query contains a LEFT JOIN that contains an OR 68 can cause a segfault if a query contains a LEFT JOIN that contains an OR 69 in the ON clause. 69 in the ON clause. 70 } 70 } 71 71 ................................................................................................................................................................................ 87 interface differs from sqlite3_close() in that it is designed to work 87 interface differs from sqlite3_close() in that it is designed to work 88 better for host language that use a garbage collector. With the older 88 better for host language that use a garbage collector. With the older 89 sqlite3_close() interface, the associated [prepared statements] and 89 sqlite3_close() interface, the associated [prepared statements] and 90 [sqlite3_backup] objects must be destroyed before the database connection. 90 [sqlite3_backup] objects must be destroyed before the database connection. 91 With the newer sqlite3_close_v2() interface, the objects can be destroyed 91 With the newer sqlite3_close_v2() interface, the objects can be destroyed 92 in any order. 92 in any order. 93 93 94 This release also includes preformance improvements to the sort algorithm | 94 This release also includes performance improvements to the sort algorithm 95 that is used to implement ORDER BY and CREATE INDEX. And the query planner 95 that is used to implement ORDER BY and CREATE INDEX. And the query planner 96 has been enhanced to better use covering indices on queries that use OR 96 has been enhanced to better use covering indices on queries that use OR 97 terms in the WHERE clause. 97 terms in the WHERE clause. 98 } 98 } 99 99 100 newsitem {2012-June-11} {Release 3.7.13} { 100 newsitem {2012-June-11} {Release 3.7.13} { 101 SQLite [version 3.7.13] adds support for WinRT and metro style 101 SQLite [version 3.7.13] adds support for WinRT and metro style