Documentation Source Text

}

chng {2015-11-01 (3.9.0)} {
<p><b>Policy Changes:</b>
<li>The [version numbering conventions] for SQLite are revised to use the
    emerging standard of [http://semver.org/|semantic versioning].
<p><b>New Features And Enhancements:</b>
<li>Added [the json1 extension] module in the source tree.



<li>The [CREATE VIEW] statement now accepts an optional list of
    column names following the view name.
<li>Added support for [indexes on expressions].
<li>Added support for [table-valued functions] in the FROM clause of a
    [SELECT] statement.
<li>Added support for [eponymous virtual tables].
<li>A [VIEW] may now reference undefined tables and functions when

}

chng {2015-11-01 (3.9.0)} {
<p><b>Policy Changes:</b>
<li>The [version numbering conventions] for SQLite are revised to use the
    emerging standard of [http://semver.org/|semantic versioning].
<p><b>New Features And Enhancements:</b>
<li>Added [the json1 extension] module in the source tree, and in the [amalgamation].
    Enable support using the [SQLITE_ENABLE_JSON1] compile-time option.
<li>Added [FTS5|Full Text Search version 5 (FTS5)] to the [amalgamation], enabled
    using [SQLITE_ENABLE_FTS5].  FTS5 is now considered official and supported.
<li>The [CREATE VIEW] statement now accepts an optional list of
    column names following the view name.
<li>Added support for [indexes on expressions].
<li>Added support for [table-valued functions] in the FROM clause of a
    [SELECT] statement.
<li>Added support for [eponymous virtual tables].
<li>A [VIEW] may now reference undefined tables and functions when

  and also allows query expressions to contain nested parenthesis.
}

COMPILE_OPTION {SQLITE_ENABLE_FTS4} {
  When this option is defined in the [amalgamation], versions 3 and 4
  of the full-text search engine is added to the build automatically.
}






COMPILE_OPTION {SQLITE_ENABLE_ICU} {
  This option causes the 
  [http://www.icu-project.org/ | International Components for Unicode]
  or "ICU" extension to SQLite to be added to the build.  
}

COMPILE_OPTION {SQLITE_ENABLE_IOTRACE} {
  When both the SQLite core and the [Command Line Interface] (CLI) are both 
  compiled with this option, then the CLI provides an extra command
  named ".iotrace" that provides a low-level log of I/O activity.
  This option is experimental and may be discontinued in a future release.
}






COMPILE_OPTION {SQLITE_ENABLE_LOCKING_STYLE} {
  This option enables additional logic in the OS interface layer for
  Mac OS X. The additional logic attempts to determine the type of the
  underlying filesystem and choose and alternative locking strategy
  that works correctly for that filesystem type. Five locking strategies 
  are available:

  and also allows query expressions to contain nested parenthesis.
}

COMPILE_OPTION {SQLITE_ENABLE_FTS4} {
  When this option is defined in the [amalgamation], versions 3 and 4
  of the full-text search engine is added to the build automatically.
}

COMPILE_OPTION {SQLITE_ENABLE_FTS5} {
  When this option is defined in the [amalgamation], versions 5
  of the full-text search engine ([fts5]) is added to the build automatically.
}

COMPILE_OPTION {SQLITE_ENABLE_ICU} {
  This option causes the 
  [http://www.icu-project.org/ | International Components for Unicode]
  or "ICU" extension to SQLite to be added to the build.  
}

COMPILE_OPTION {SQLITE_ENABLE_IOTRACE} {
  When both the SQLite core and the [Command Line Interface] (CLI) are both 
  compiled with this option, then the CLI provides an extra command
  named ".iotrace" that provides a low-level log of I/O activity.
  This option is experimental and may be discontinued in a future release.
}

COMPILE_OPTION {SQLITE_ENABLE_JSON1} {
  When this option is defined in the [amalgamation], the
  [JSON SQL functions] are added to the build automatically.
}

COMPILE_OPTION {SQLITE_ENABLE_LOCKING_STYLE} {
  This option enables additional logic in the OS interface layer for
  Mac OS X. The additional logic attempts to determine the type of the
  underlying filesystem and choose and alternative locking strategy
  that works correctly for that filesystem type. Five locking strategies 
  are available:

option:</p>

<blockquote><pre>
gcc -DSQLITE_THREADSAFE=0 -DSQLITE_OMIT_LOAD_EXTENSION shell.c sqlite3.c
</pre></blockquote>

<p>One might want to provide other [compile-time options] such as
[SQLITE_ENABLE_FTS3 | -DSQLITE_ENABLE_FTS3] for full-text search or
[SQLITE_ENABLE_RTREE | -DSQLITE_ENABLE_RTREE]
for the R*Tree search engine extension.  In order to see extra commentary


in [EXPLAIN] listings, add the 
[SQLITE_ENABLE_EXPLAIN_COMMENTS | -DSQLITE_ENABLE_EXPLAIN_COMMENTS] option.
On unix systems, add -DHAVE_USLEEP=1 if the host machine supports the
usleep() system call.  Add -DHAVE_READLINE and the -lreadline
and -lncurses libraries to get command-line editing support.
One might also want to
specify some compiler optimization switches.  (The precompiled

option:</p>

<blockquote><pre>
gcc -DSQLITE_THREADSAFE=0 -DSQLITE_OMIT_LOAD_EXTENSION shell.c sqlite3.c
</pre></blockquote>

<p>One might want to provide other [compile-time options] such as
[SQLITE_ENABLE_FTS5 | -DSQLITE_ENABLE_FTS4] for full-text search or
[SQLITE_ENABLE_RTREE | -DSQLITE_ENABLE_RTREE]
for the R*Tree search engine extension or
[SQLITE_ENABLE_JSON1 | -DSQLITE_ENABLE_JSON1] to include
[JSON SQL functions].  In order to see extra commentary
in [EXPLAIN] listings, add the 
[SQLITE_ENABLE_EXPLAIN_COMMENTS | -DSQLITE_ENABLE_EXPLAIN_COMMENTS] option.
On unix systems, add -DHAVE_USLEEP=1 if the host machine supports the
usleep() system call.  Add -DHAVE_READLINE and the -lreadline
and -lncurses libraries to get command-line editing support.
One might also want to
specify some compiler optimization switches.  (The precompiled

<title>The JSON1 Extension</title>
<tcl>hd_keywords json1 {the json1 extension}</tcl>
<h2>The JSON1 Extension</h2>

<p>
The <b>json1</b> extension is a [loadable extension] that
implements eleven [application-defined SQL functions] and
two [table-valued functions] that are useful for
managing JSON content stored in an SQLite database.

<title>The JSON1 Extension</title>
<tcl>hd_keywords json1 {the json1 extension} {JSON SQL functions}</tcl>
<h2>The JSON1 Extension</h2>

<p>
The <b>json1</b> extension is a [loadable extension] that
implements eleven [application-defined SQL functions] and
two [table-valued functions] that are useful for
managing JSON content stored in an SQLite database.