Documentation Source Text

Check-in [67c02fcc03]
Login

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.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 67c02fcc03315f7fb3019bf30dd6bf9ba9ab0481
User & Date: dan 2009-03-04 12:20:46
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
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/lang.in.

  1878   1878   The aggregate functions shown below are available by default.  Additional
  1879   1879   aggregate functions written in C may be added using the 
  1880   1880   [sqlite3_create_function()]</a>
  1881   1881   API.</p>
  1882   1882   
  1883   1883   <p>
  1884   1884   In any aggregate function that takes a single argument, that argument
  1885         -can be preceeded by the keyword DISTINCT.  In such cases, duplicate
         1885  +can be preceded by the keyword DISTINCT.  In such cases, duplicate
  1886   1886   elements are filtered before being passed into the aggregate function.
  1887   1887   For example, the function "count(distinct X)" will return the number
  1888   1888   of distinct values of column X instead of the total number of non-null
  1889   1889   values in column X.
  1890   1890   </p>
  1891   1891   
  1892   1892   <table border=0 cellpadding=10>
................................................................................
  2304   2304   
  2305   2305   <tcl>
  2306   2306   BubbleDiagram qualified-table-name
  2307   2307   BubbleDiagram single-source
  2308   2308   </tcl>
  2309   2309   
  2310   2310   <p>The "INDEXED BY index-name" clause specifies that the named index
  2311         -must be used in order to look up values on the preceeding table.
         2311  +must be used in order to look up values on the preceding table.
  2312   2312   If index-name does not exist or cannot be used for the query, then
  2313   2313   the preparation of the SQL statement fails.
  2314   2314   The "NOT INDEXED" clause specifies that no index shall be used when
  2315         -accessing the preceeding table, including implied indices create by
         2315  +accessing the preceding table, including implied indices create by
  2316   2316   UNIQUE and PRIMARY KEY constraints.  However, the INTEGER PRIMARY KEY
  2317   2317   can still be used to look up entries even when "NOT INDEXED" is specified.</p>
  2318   2318   
  2319   2319   <p>Some SQL database engines provide non-standard "hint" mechanisms which
  2320   2320   can be used to give the query optimizer clues about what indices it should
  2321   2321   use for a particular statement.  The INDEX BY clause of SQLite is 
  2322   2322   <em>not</em> a hinting mechanism and it should not be used as such.

Changes to pages/pragma.in.

   413    413       for example:</p>
   414    414   
   415    415       <blockquote>
   416    416   PRAGMA <b>main.</b>locking_mode=EXCLUSIVE;
   417    417       </blockquote>
   418    418   
   419    419       <p>Then the locking mode applies only to the named database.  If no
   420         -    database name qualifier preceeds the "locking_mode" keyword then
          420  +    database name qualifier precedes the "locking_mode" keyword then
   421    421       the locking mode is applied to all databases, including any new
   422    422       databases added by subsequent [ATTACH] commands.</p>
   423    423   
   424    424      <p>The "temp" database (in which TEMP tables and indices are stored)
   425    425      always uses exclusive locking mode.  The locking mode of temp cannot
   426    426      be changed.  All other databases use the normal locking mode by default
   427    427      and are affected by this pragma.</p>

Changes to pages/testing.in.

   464    464   }
   465    465   </pre></blockquote>
   466    466   
   467    467   <p>For bitmask tests, testcase() macros are used to verify that every
   468    468   bit of the bitmask effects the test.  For example, in the following block
   469    469   of code, the condition is true if the mask contains either of two bits
   470    470   indicating either a MAIN_DB or a TEMP_DB is being opened.  The testcase()
   471         -macros that preceed the if statement verify that both cases are tested:</p>
          471  +macros that precede the if statement verify that both cases are tested:</p>
   472    472   
   473    473   <blockquote><pre>
   474    474   testcase( mask & SQLITE_OPEN_MAIN_DB );
   475    475   testcase( mask & SQLITE_OPEN_TEMP_DB );
   476    476   if( (mask & (SQLITE_OPEN_MAIN_DB|SQLITE_OPEN_TEMP_DB))!=0 ){ ... }
   477    477   </pre></blockquote>
   478    478