Documentation Source Text

    prior to 3.3.0 (2006-01-10).  It also means that the [descending indices]
    are enabled by default.
<li>The sqlite3_pcache_methods structure and the [SQLITE_CONFIG_PCACHE]
    and [SQLITE_CONFIG_GETPCACHE] configuration parameters are deprecated.
    They are replaced by a new [sqlite3_pcache_methods2] structure and
    [SQLITE_CONFIG_PCACHE2] and [SQLITE_CONFIG_GETPCACHE2] configuration
    parameters.




<li>Added the [sqlite3_db_release_memory()] interface and the
    [shrink_memory pragma].
<li>Added the [sqlite3_db_filename()] interface.
<li>Added the [sqlite3_stmt_busy()] interface.


<li>Enhance the query planner to support index queries with range constraints
    on the rowid.






<li>Enhanced the windows [VFS] so that all system calls can be overridden
    using the xSetSystemCall interface.
<li>Updated the "unix-dotfile" [VFS] to use locking directories with mkdir()
    and rmdir() instead of locking files with open() and unlink().


<li>Fix the unix [VFS] to be tolerate of read() system calls that return 
    less then the full number of requested bytes.












}

chng {2011 November 1 (3.7.9)} {
<li>If a search token (on the right-hand side of the MATCH operator) in
    [FTS4] begins with "&#94;" then that token must be the first in its field
    of the document.  <b>** Potentially Incompatible Change **</b>
<li>Added options [SQLITE_DBSTATUS_CACHE_HIT] and [SQLITE_DBSTATUS_CACHE_MISS]

    prior to 3.3.0 (2006-01-10).  It also means that the [descending indices]
    are enabled by default.
<li>The sqlite3_pcache_methods structure and the [SQLITE_CONFIG_PCACHE]
    and [SQLITE_CONFIG_GETPCACHE] configuration parameters are deprecated.
    They are replaced by a new [sqlite3_pcache_methods2] structure and
    [SQLITE_CONFIG_PCACHE2] and [SQLITE_CONFIG_GETPCACHE2] configuration
    parameters.
<li>Added the [powersafe overwrite] property to the VFS interface.  Provide
    the [SQLITE_IOCAP_POWERSAFE_OVERWRITE] I/O capability, the
    [SQLITE_POWERSAFE_OVERWRITE] compile-time option, and the
    "psow=BOOLEAN" query parameter for [URI filenames].
<li>Added the [sqlite3_db_release_memory()] interface and the
    [shrink_memory pragma].
<li>Added the [sqlite3_db_filename()] interface.
<li>Added the [sqlite3_stmt_busy()] interface.
<li>Enhanced the default memory allocator to make use of _msize() on windows,
    malloc_size() on Mac, and malloc_usable_size() on Linux.
<li>Enhanced the query planner to support index queries with range constraints
    on the rowid.
<li>Enhanced the query planner flattening logic to allow UNION ALL compounds
    to be promoted upwards to replace a simple wrapper SELECT even if the
    compounds are joins.
<li>Enhanced the query planner so that the xfer optimization can be used with
    INTEGER PRIMARY KEY ON CONFLICT as long as the destination table is
    initially empty.
<li>Enhanced the windows [VFS] so that all system calls can be overridden
    using the xSetSystemCall interface.
<li>Updated the "unix-dotfile" [VFS] to use locking directories with mkdir()
    and rmdir() instead of locking files with open() and unlink().
<li>Enhancements to the test_quota.c extension to support stdio-like interfaces
    with quotas.
<li>Change the unix [VFS] to be tolerant of read() system calls that return 
    less then the full number of requested bytes.
<li><b>Bug fix:</b>
    Add an additional xSync when restarting a WAL in order to prevent an
    exceedingly unlikely but theoretically possible
    database corruption following power-loss.
    Ticket [http://www.sqlite.org/src/info/ff5be73dee | ff5be73dee].
<li><b>Bug fix:</b>
    Change the VDBE so that all registers are initialized to Invalid
    instead of NULL.
    Ticket [http://www.sqlite.org/src/info/7bbfb7d442 | 7bbfb7d442]
<li><b>Bug fix:</b>
    Fix problems that can result from 32-bit integer overflow.
    Ticket [http://www.sqlite.org/src/info/ac0ff496b7e2 | ac00f496b7e2]
}

chng {2011 November 1 (3.7.9)} {
<li>If a search token (on the right-hand side of the MATCH operator) in
    [FTS4] begins with "&#94;" then that token must be the first in its field
    of the document.  <b>** Potentially Incompatible Change **</b>
<li>Added options [SQLITE_DBSTATUS_CACHE_HIT] and [SQLITE_DBSTATUS_CACHE_MISS]

<h2>2.0 List Of Requirements</h2>

<dl>
<tcl>
db eval {SELECT * FROM requirement ORDER BY reqno} {
  hd_puts "<dt><b>$reqno</b></dt>"
  hd_puts "<dd><p>$reqtext <i>(source: $srcfile)</i></p></dd>"










}
</tcl>
</dl>

<h2>2.0 List Of Requirements</h2>

<dl>
<tcl>
db eval {SELECT * FROM requirement ORDER BY reqno} {
  hd_puts "<dt><b>$reqno</b></dt>\n"
  hd_puts "<dd><p>$reqtext\n"
  set ck [
    db eval {SELECT DISTINCT srccat || '/' || srcfile FROM evidence
             WHERE reqno=$reqno ORDER BY 1}
  ]
  if {[llength $ck]==0} {
    hd_puts "<i>(source: $srcfile)</i>"
  } else {
    hd_puts "<i>(source: $srcfile, checked-by: [join $ck {, }])</i>"
  }
  hd_puts "</p></dd>\n\n"
}
</tcl>
</dl>