Documentation Source Text

}

chng {2016-03-00 (3.11.0)} {
<p><b>General improvements:</b>
<li>Enhanced [WAL mode] so that it works efficiently with transactions that are
    larger than the [cache_size].
<li>Added the [FTS5 detail option].


<li>Added the [SQLITE_EXTRA_DURABLE] compile-time option.

<li>Enhanced the [query planner] so that it is able to use
    a [covering index] as part of the [OR optimization].
<li>Many micro-optimizations, resulting in a library that is both smaller
    and faster than the previous release.
<p><b>Enhancements to the [command-line shell]:</b>
<li>Added the ".vfslist" [dot-commands|dot-command].
<p><b>Enhancements to the [TCL Interface]:</b>

  the [SQLITE_LIMIT_WORKER_THREADS] parameter.  The [SQLITE_LIMIT_WORKER_THREADS]
  parameter sets the maximum number of auxiliary threads that a single
  [prepared statement] will launch to assist it with a query.  If not specified,
  the default maximum is 0.
  The value set here cannot be more than [SQLITE_MAX_WORKER_THREADS].
}

COMPILE_OPTION {SQLITE_EXTRA_DURABLE=<i>&lt;0 or 1&gt;</i>} {
  If the SQLITE_EXTRA_DURABLE=1 compile-time option is used then SQLite works
  harder to make transactions durable across power failures.
  The default behavior (SQLITE_EXTRA_DURABLE=0) is that the a committed transaction
  might rollback following recovery from a power loss.
  The default behavior is faster and since
  most applications prefer extra performance and are happy to
  endure an occasional rollback following a power-loss recovery.
  Applications for which transaction durability is more important can set
  this compile-time option for extra protection.
  <p>
  In the current implementation ([version 3.11.0]), this option only makes a
  difference when committing a transaction in [PRAGMA journal_mode=DELETE]
  and [PRAGMA synchronous=FULL].  In that scenario, the directory containing the
  rollback journal is synced after the rollback journal is deleted, to ensure
  that the rollback journal stays deleted after recovery from power loss.
  <p>
  Additional notes:
  <ol>
  <li><p>
  This option only affects transaction durability following power loss.
  The default configuration always ensures consistency, including after 
  a power loss, and ensures durable in the absence of a power loss, 
  regardless of this setting.
  <li><p>
  [PRAGMA synchronous=FULL] must be set at run time, in addition to this
  compile-time option, for power-loss durability.  
  FULL synchronous is the default when using a [rollback journal]
  but NORMAL synchronous is the default for [WAL mode].
  <li><p>
  Transactions are consistent and durable across power-loss with
  [PRAGMA journal_mode=TRUNCATE] and [PRAGMA journal_mode=PERSIST] and
  [PRAGMA journal_mode=WAL] even
  without this compile-time option, as long as [PRAGMA synchronous=FULL] is set.
  </ol>
}

COMPILE_OPTION {SQLITE_FTS3_MAX_EXPR_DEPTH=<i>N</i>} {
  This macro sets the maximum depth of the search tree that corresponds to
  the right-hand side of the MATCH operator in an [FTS3] or [FTS4] full-text
  index.  The full-text search uses a recursive algorithm, so the depth of
  the tree is limited to prevent using too much stack space.  The default

    function.
    </p>
}

Pragma synchronous {
    <p>^(<b>PRAGMA DB.synchronous;
        <br>PRAGMA DB.synchronous = </b>
          <i>0 | OFF | 1 | NORMAL | 2 | FULL</i><b>;</b></p>

    <p>Query or change the setting of the "synchronous" flag.)^
    ^The first (query) form will return the synchronous setting as an 











    integer.  ^When synchronous is FULL (2), the SQLite database engine will
    use the xSync method of the [VFS] to ensure that all content is safely
    written to the disk surface prior to continuing.
    This ensures that an operating system crash or power failure will
    not corrupt the database.
    FULL synchronous is very safe, but it is also slower. 



    ^When synchronous is NORMAL (1), the SQLite database
    engine will still sync at the most critical moments, but less often
    than in FULL mode.  There is a very small (though non-zero) chance that
    a power failure at just the wrong time could corrupt the database in
    NORMAL mode.  But in practice, you are more likely to suffer
    a catastrophic disk failure or some other unrecoverable hardware
    fault.


    ^With synchronous OFF (0), SQLite continues without syncing
    as soon as it has handed data off to the operating system.
    If the application running SQLite crashes, the data will be safe, but
    the database might become corrupted if the operating system
    crashes or the computer loses power before that data has been written
    to the disk surface.  On the other hand, some
    operations are as much as 50 or more times faster with synchronous OFF.

    </p>
 
    <p>^In [WAL] mode when synchronous is NORMAL (1), the WAL file is
    synchronized before each [checkpoint] and the database file is
    synchronized after each completed [checkpoint] and the WAL file
    header is synchronized when a WAL file begins to be reused after
    a checkpoint, but no sync operations occur during most transactions.
    ^With synchronous=FULL in WAL mode, an additional
    sync operation of the WAL file happens after each transaction commit.
    The extra WAL sync following each transaction help ensure that 
    transactions are durable across a power loss, but they do not aid
    in preserving consistency.
    If durability is not a concern, then synchronous=NORMAL is normally
    all one needs in WAL mode.</p>

    <p>^The default setting is synchronous=FULL, except in [WAL mode] when
    the default is synchronous=NORMAL.</p>



    <p>See also the [fullfsync] and [checkpoint_fullfsync] pragmas.</p>
}

Pragma temp_store {
    <p>^(<b>PRAGMA temp_store;
        <br>PRAGMA temp_store = </b>