Documentation Source Text

Check-in [9d6e96fd8f]
Login

Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.

Overview
Comment:Merge changes from the 3.26.0 release branch.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256:9d6e96fd8f1eb54572452fbf36006df7c2413fd693b43788ef02b033985ca02c
User & Date: drh 2019-02-07 13:47:38
Context
2019-02-07
13:59
Add back the sponsors section to the front page. check-in: 3b7ad43873 user: drh tags: trunk
13:47
Merge changes from the 3.26.0 release branch. check-in: 9d6e96fd8f user: drh tags: trunk
13:42
Add news for 3.27.0 check-in: 7a25788e4c user: drh tags: trunk
2019-01-29
18:59
Fix a typo in the date-time function documentation. Leaf check-in: 0866c95aaf user: drh tags: branch-3.26
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/assert.in.

   199    199   running off the end of the linked list in case there is an error in some
   200    200   other part of the code that has corrupted the linked list.
   201    201   
   202    202   <p>
   203    203   An ALWAYS(X) or NEVER(X) sometimes verifies pre-conditions that are
   204    204   subject to change if other parts of the code are modified in
   205    205   subtle ways.  At [https://sqlite.org/src/artifact/18a53540aa3?ln=5512-5516]
   206         -we have a case test for two pre-conditions that are true only because
          206  +we have a test for two pre-conditions that are true only because
   207    207   of the limited scope of use of the sqlite3BtreeRowCountEst() function.
   208    208   Future enhancements to SQLite might use sqlite3BtreeRowCountEst() in
   209    209   new ways where those preconditions no longer hold, and the NEVER()
   210    210   macros will quickly alert the developers to that fact when the
   211    211   situation arises.  But if, for some reason, the pre-conditions are
   212    212   not satisfied in a release build, the program will still behave sanely
   213    213   and will not do an undefined memory access.
   214    214   
   215    215   <p>
   216    216   The testcase() macro is often used to verify that boundary
   217    217   cases of an inequality comparison are checked.  For example, at
   218    218   [https://sqlite.org/src/artifact/18a53540aa3?ln=5766].  These
   219    219   kind of checks help to prevent off-by-one errors.

Changes to pages/codeofethics.in.

    17     17   specific technical requirements was inserted in the place of
    18     18   the old name.
    19     19   
    20     20   <p>
    21     21   This document is still sometimes used as a "Code of Conduct" on supplier
    22     22   registration forms.  But it is not a Code of Conduct in the same sense
    23     23   that many communities mean a Code of Conduct.  Rather,
    24         -this document describes the ethical principals upon
           24  +this document describes the ethical principles upon
    25     25   which SQLite is based.  Another way to look at this document is
    26     26   as a succinct description of the SQLite Founder's idea of what it
    27     27   means to be "virtuous".
    28     28   
    29     29   <p>
    30     30   Readers can also interpret this document as a primer on the
    31     31   world-view of the SQLite Founder, to help them better understand

Changes to pages/lang.in.

  3227   3227   localtime_r() C function normally only works for years
  3228   3228   between 1970 and 2037. For dates outside this range, SQLite 
  3229   3229   attempts to map the year into an equivalent year within 
  3230   3230   this range, do the calculation, then map the year back.)^</p>
  3231   3231   
  3232   3232   
  3233   3233   <p>^(These functions only work for dates between 0000-01-01 00:00:00
  3234         -and 9999-12-31 23:59:59 (julidan day numbers 1721059.5 through 5373484.5).)^
         3234  +and 9999-12-31 23:59:59 (julian day numbers 1721059.5 through 5373484.5).)^
  3235   3235   For dates outside that range, the results of these
  3236   3236   functions are undefined.</p>
  3237   3237   
  3238   3238   <p>Non-Vista Windows platforms only support one set of DST rules. 
  3239   3239   Vista only supports two. Therefore, on these platforms, 
  3240   3240   historical DST calculations will be incorrect. 
  3241   3241   For example, in the US, in 2007 the DST rules changed. 

Changes to pages/pragma.in.

  1387   1387       database connection.</p>)^
  1388   1388   }
  1389   1389   
  1390   1390   Pragma database_list {
  1391   1391       <p>^(<b>PRAGMA database_list;</b></p>
  1392   1392       <p>This pragma works like a query to return one row for each database
  1393   1393       attached to the current database connection.)^
  1394         -    ^(The second column is the "main" for the main database file, "temp"
         1394  +    ^(The second column is "main" for the main database file, "temp"
  1395   1395       for the database file used to store TEMP objects, or the name of the
  1396   1396       ATTACHed database for other database files.)^
  1397   1397       ^(The third column is the name of the database file itself, or an empty
  1398   1398       string if the database is not associated with a file.)^</p>
  1399   1399   }
  1400   1400   
  1401   1401   Pragma foreign_key_list {

Changes to pages/security.in.

     3      3     {defense against dark arts}</tcl>
     4      4   <fancy_format>
     5      5   
     6      6   <h1>SQLite Always Validates Its Inputs</h1>
     7      7   
     8      8   <p>
     9      9   SQLite should never crash, overflow a buffer, leak memory,
    10         -or exhibit any other harmful behavior, even with presented with
           10  +or exhibit any other harmful behavior, even when presented with
    11     11   maliciously malformed SQL inputs or database files.  SQLite should
    12     12   always detect erroneous inputs and raise an error, not crash or
    13     13   corrupt memory.
    14     14   Any malfunction caused by an SQL input or database file
    15     15   is considered a serious bug and will be promptly addressed when
    16     16   brought to the attention of the SQLite developers.  SQLite is
    17     17   extensively fuzz-tested to help ensure that it is resistant