Documentation Source Text

Check-in [41f9becb46]
Login

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

Overview
Comment:Begin a new change log entries for 3.27.0.
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 41f9becb4667ad0de8327a2d8f94f4d72e2753ec5d393fc8dd253f82f59aee2f
User & Date: drh 2018-12-10 00:52:32
Context
2018-12-10
11:48
Update the change log. check-in: 22f1dff034 user: drh tags: trunk
00:52
Begin a new change log entries for 3.27.0. check-in: 41f9becb46 user: drh tags: trunk
2018-12-09
22:30
Omit the sponsor links from the homepage. check-in: 3c035c0759 user: drh tags: trunk
Changes
Hide Diffs Side-by-Side Diffs Ignore Whitespace Patch

Changes to pages/changes.in.

    16     16   set nChng 0
    17     17   proc chng {date desc {options {}}} {
    18     18     global nChng aChng xrefChng
    19     19     set aChng($nChng) [list $date $desc $options]
    20     20     set xrefChng($date) $nChng
    21     21     incr nChng
    22     22   }
           23  +
           24  +chng {2019-02-00 (3.27.0)} {
           25  +<li>Added the [VACUUM INTO] command
           26  +<li>Issue an SQLITE_WARNING message on the [error log] if a 
           27  +[double-quoted string literal] is used.
           28  +}
    23     29   
    24     30   chng {2018-12-01 (3.26.0)} {
    25     31   <li>Optimization: When doing an [UPDATE] on a table with [indexes on expressions],
    26     32       do not update the expression indexes if they do not refer to any of the columns
    27     33       of the table being updated.
    28     34   <li>Allow the [xBestIndex()] method of [virtual table] implementations to return
    29     35       [SQLITE_CONSTRAINT] to indicate that the proposed query plan is unusable and

Changes to pages/chronology.in.

    24     24   #    ORDER BY mtime DESC;
    25     25   #
    26     26   # A small amount of manual editing and de-duplication followed.
    27     27   #
    28     28   # Manually edit the list for each subsequent release.
    29     29   #      
    30     30   foreach line [split {
           31  +xxxxxxxxxx|pending|Version 3.27.0
    31     32   bf8c1b2b7a|2018-12-01|Version 3.26.0
    32     33   89e099fbe5|2018-11-05|Version 3.25.3
    33     34   fb90e7189a|2018-09-25|Version 3.25.2
    34     35   2ac9003de4|2018-09-18|Version 3.25.1
    35     36   b63af6c3bd|2018-09-15|Version 3.25.0
    36     37   c7ee083322|2018-06-04|Version 3.24.0
    37     38   4bb2294022|2018-04-10|Version 3.23.1

Changes to pages/index.in.

     5      5   [full-featured SQL|full-featured], [public-domain],
     6      6   SQL database engine.
     7      7   SQLite is the [most used] database engine in the world.
     8      8   <a class="button" href="about.html">More Info</a></p>
     9      9   
    10     10   <hr class="xhr">
    11     11   <span class="hdrfont">Latest Release:&nbsp;&nbsp;</span>
    12         -<a href="releaselog/3_25_2.html">Version 3.25.2</a> ([dateof:3.25.2]).
           12  +<a href="releaselog/3_27_0.html">Version 3.27.0</a> ([dateof:3.27.0]).
    13     13   <a class="button" href="download.html">Download</a>
    14     14   <a class="button" href="chronology.html">Prior Releases</a>
    15     15   
    16     16   <hr class="xhr">
    17     17   <h3>Common Links</h3>
    18     18   <tcl>common_links</tcl>

Changes to pages/lang.in.

  4963   4963   
  4964   4964     <li> <p> When content is deleted from an SQLite database, the content is not
  4965   4965        usually erased but rather the space used to hold the content is marked as
  4966   4966        being available for reuse.  This can allow deleted content to be recovered
  4967   4967        by a hacker or by forensic analysis.  Running VACUUM will clean the database
  4968   4968        of all traces of deleted content, thus preventing an adversary from recovering
  4969   4969        deleted content.  Using VACUUM in this way is an alternative to setting
  4970         -     [PRAGMA security_delete=ON]. 
         4970  +     [PRAGMA secure_delete=ON]. 
  4971   4971   
  4972   4972     <li> <p> ^Normally, the database [page_size] and whether or not the database
  4973   4973        supports [auto_vacuum] must be configured before the database file is
  4974   4974        actually created. ^However, when not in [write-ahead log] mode, the 
  4975   4975        [page_size] and/or [auto_vacuum] properties of an existing database may be
  4976   4976        changed by using the [page_size pragma|page_size]  and/or 
  4977   4977        [auto_vacuum|pragma auto_vacuum] pragmas and then immediately VACUUMing

Changes to pages/quirks.in.

   228    228   </ol>
   229    229   <p>
   230    230   Full unicode case folding is supported in SQLite if it is compiled
   231    231   with the [-DSQLITE_ENABLE_ICU] option and linked against the
   232    232   [http://site.icu-project.org/|International Components for Unicode]
   233    233   library.
   234    234   
          235  +<tcl>hd_fragment dblquote {double-quoted string literal}</tcl>
   235    236   <h1>Double-quoted String Literals Are Accepted</h1>
   236    237   
   237    238   <p>
   238    239   The SQL standard says that one should use double-quotes around identifiers
   239    240   and single-quotes around string literals.
   240    241   <ul>
   241    242   <li> <tt>"this is a legal SQL column name"</tt>
................................................................................
   254    255   the SQL language to continue using double-quoted string literals when they
   255    256   really need to learn to use the correct single-quoted string literal form.
   256    257   <p>
   257    258   In hindsight, we should not have tried to make SQLite accept MySQL 3.x
   258    259   syntax, and should have never allowed double-quoted string literals.
   259    260   However, we continue to support that capability to avoid breaking legacy
   260    261   applications.
          262  +<p>
          263  +Update: As of SQLite 3.27.0 ([dateof:3.27.0]) the use of a double-quoted
          264  +string literal causes a warning message to be sent to the [error log].
   261    265   
   262    266   <h1>Keywords Can Often Be Used As Identifiers</h1>
   263    267   
   264    268   <p>
   265    269   The SQL language is rich in keywords.
   266    270   Most SQL implementations do not allow keywords to be used as identifiers
   267    271   (the names of table or columns) unless they are enclosed in double-quotes.