Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Fix spelling of precede and preceding in a few places. Cvs ticket 3700. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk |
Files: | files | file ages | folders |
SHA1: |
67c02fcc03315f7fb3019bf30dd6bf9b |
User & Date: | dan 2009-03-04 12:20:46.000 |
Context
2009-03-05
| ||
21:46 | Fixed some typos and spelling mistakes. (check-in: 832ea9eb72 user: shaneh tags: trunk) | |
2009-03-04
| ||
12:20 | Fix spelling of precede and preceding in a few places. Cvs ticket 3700. (check-in: 67c02fcc03 user: dan tags: trunk) | |
2009-02-23
| ||
18:14 | Added the beginnings of a change log for version 3.6.12. (check-in: c926b561a2 user: drh tags: trunk) | |
Changes
Changes to pages/lang.in.
︙ | ︙ | |||
1878 1879 1880 1881 1882 1883 1884 | The aggregate functions shown below are available by default. Additional aggregate functions written in C may be added using the [sqlite3_create_function()]</a> API.</p> <p> In any aggregate function that takes a single argument, that argument | | | 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 | The aggregate functions shown below are available by default. Additional aggregate functions written in C may be added using the [sqlite3_create_function()]</a> API.</p> <p> In any aggregate function that takes a single argument, that argument can be preceded by the keyword DISTINCT. In such cases, duplicate elements are filtered before being passed into the aggregate function. For example, the function "count(distinct X)" will return the number of distinct values of column X instead of the total number of non-null values in column X. </p> <table border=0 cellpadding=10> |
︙ | ︙ | |||
2304 2305 2306 2307 2308 2309 2310 | <tcl> BubbleDiagram qualified-table-name BubbleDiagram single-source </tcl> <p>The "INDEXED BY index-name" clause specifies that the named index | | | | 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 | <tcl> BubbleDiagram qualified-table-name BubbleDiagram single-source </tcl> <p>The "INDEXED BY index-name" clause specifies that the named index must be used in order to look up values on the preceding table. If index-name does not exist or cannot be used for the query, then the preparation of the SQL statement fails. The "NOT INDEXED" clause specifies that no index shall be used when accessing the preceding table, including implied indices create by UNIQUE and PRIMARY KEY constraints. However, the INTEGER PRIMARY KEY can still be used to look up entries even when "NOT INDEXED" is specified.</p> <p>Some SQL database engines provide non-standard "hint" mechanisms which can be used to give the query optimizer clues about what indices it should use for a particular statement. The INDEX BY clause of SQLite is <em>not</em> a hinting mechanism and it should not be used as such. |
︙ | ︙ |
Changes to pages/pragma.in.
︙ | ︙ | |||
413 414 415 416 417 418 419 | for example:</p> <blockquote> PRAGMA <b>main.</b>locking_mode=EXCLUSIVE; </blockquote> <p>Then the locking mode applies only to the named database. If no | | | 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 | for example:</p> <blockquote> PRAGMA <b>main.</b>locking_mode=EXCLUSIVE; </blockquote> <p>Then the locking mode applies only to the named database. If no database name qualifier precedes the "locking_mode" keyword then the locking mode is applied to all databases, including any new databases added by subsequent [ATTACH] commands.</p> <p>The "temp" database (in which TEMP tables and indices are stored) always uses exclusive locking mode. The locking mode of temp cannot be changed. All other databases use the normal locking mode by default and are affected by this pragma.</p> |
︙ | ︙ |
Changes to pages/testing.in.
︙ | ︙ | |||
464 465 466 467 468 469 470 | } </pre></blockquote> <p>For bitmask tests, testcase() macros are used to verify that every bit of the bitmask effects the test. For example, in the following block of code, the condition is true if the mask contains either of two bits indicating either a MAIN_DB or a TEMP_DB is being opened. The testcase() | | | 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 | } </pre></blockquote> <p>For bitmask tests, testcase() macros are used to verify that every bit of the bitmask effects the test. For example, in the following block of code, the condition is true if the mask contains either of two bits indicating either a MAIN_DB or a TEMP_DB is being opened. The testcase() macros that precede the if statement verify that both cases are tested:</p> <blockquote><pre> testcase( mask & SQLITE_OPEN_MAIN_DB ); testcase( mask & SQLITE_OPEN_TEMP_DB ); if( (mask & (SQLITE_OPEN_MAIN_DB|SQLITE_OPEN_TEMP_DB))!=0 ){ ... } </pre></blockquote> |
︙ | ︙ |