Documentation Source Text

Check-in [110e2bb5b0]
Login

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

Overview
Comment:Fix typos in new documents.
Downloads: Tarball | ZIP archive
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA1: 110e2bb5b08bab06a3d7db82f4bf4df0dc8635b8
User & Date: drh 2015-10-12 04:46:15.279
Context
2015-10-12
05:51
More documentation updates for 3.9.0. (check-in: 1c92bfea70 user: drh tags: trunk)
04:46
Fix typos in new documents. (check-in: 110e2bb5b0 user: drh tags: trunk)
2015-10-10
09:36
Add a new example for external-content tables to fts3.html. (check-in: e68ac068e8 user: dan tags: trunk)
Changes
Unified Diff Ignore Whitespace Patch
Changes to pages/changes.in.
︙︙
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

set nChng 0
proc chng {date desc {options {}}} {
  global nChng aChng
  set aChng($nChng) [list $date $desc $options]
  incr nChng
}

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








|








14
15
16
17
18
19
20
21
22
23
24
25
26
27
28

set nChng 0
proc chng {date desc {options {}}} {
  global nChng aChng
  set aChng($nChng) [list $date $desc $options]
  incr nChng
}

chng {2015-10-19 (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
︙︙
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

<li>Added the [sqlite3_value_subtype()] and [sqlite3_result_subtype()]
    interfaced (used by [the json1 extension]).
<li>The query planner is now able to use [partial indexes] that contain
    AND-connected terms in the WHERE clause.
<li>The sqlite3_analyzer.exe utility is updated to report the depth of
    each btree and to show the average fanout for indexes and 
    WITHOUT ROWID tables.
<li>Enhance the [dbstat virtual table] so that it can be used as a
    [table-valued functions] where the argument is the schema to be
    analyzed.
<p><b>Other changes:</b>
<li>The [sqlite3_memory_alarm()] interface, which has been deprecated and
    undocumented for 8 years, is changed into a no-op.
<p><b>Important fixes:</b>
<li>Fixed a critical bug in the 
    [https://www.sqlite.org/see/doc/trunk/www/readme.wiki|SQLite Encryption Extension] that








|
|








40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55

<li>Added the [sqlite3_value_subtype()] and [sqlite3_result_subtype()]
    interfaced (used by [the json1 extension]).
<li>The query planner is now able to use [partial indexes] that contain
    AND-connected terms in the WHERE clause.
<li>The sqlite3_analyzer.exe utility is updated to report the depth of
    each btree and to show the average fanout for indexes and 
    WITHOUT ROWID tables.
<li>Enhanced the [dbstat virtual table] so that it can be used as a
    [table-valued function] where the argument is the schema to be
    analyzed.
<p><b>Other changes:</b>
<li>The [sqlite3_memory_alarm()] interface, which has been deprecated and
    undocumented for 8 years, is changed into a no-op.
<p><b>Important fixes:</b>
<li>Fixed a critical bug in the 
    [https://www.sqlite.org/see/doc/trunk/www/readme.wiki|SQLite Encryption Extension] that
︙︙
Changes to pages/versionnumbers.in.
︙︙
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35


<h2>The New Version Numbering System (After 2015-10-01)</h2>

<p>
All SQLite releases starting with 3.9.0 use a three-number
"[http://semver.org|semantic version]" of the form X.Y.Z.
The first number X is only increased when there is a change that
breaks backwards compatibility.  The
current value for X is 3, and the SQLite developers plan to support
the current SQLite databse file format, SQL syntax, and C interface
through at least the year 2050.  Hence, one
can expect that all future versions of SQLite for the next several
decades will begin with "3.".

<p>
The second number Y is incremented for any change that breaks forwards
compatibility by adding new features.
Most SQLite releases moving forward are expected
to increment the second number Y.  The Z is reset to zero whenever Y
is increased.

<p>
The third number Z is incremented for releases consisting of only
small changes that implement performance enhancements and/or bug fixes.









|







|

|








11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35


<h2>The New Version Numbering System (After 2015-10-01)</h2>

<p>
All SQLite releases starting with 3.9.0 use a three-number
"[http://semver.org|semantic version]" of the form X.Y.Z.
The first number X is only increased when there is a change that
breaks backward compatibility.  The
current value for X is 3, and the SQLite developers plan to support
the current SQLite databse file format, SQL syntax, and C interface
through at least the year 2050.  Hence, one
can expect that all future versions of SQLite for the next several
decades will begin with "3.".

<p>
The second number Y is incremented for any change that breaks forward
compatibility by adding new features.
Most future SQLite releases are expected
to increment the second number Y.  The Z is reset to zero whenever Y
is increased.

<p>
The third number Z is incremented for releases consisting of only
small changes that implement performance enhancements and/or bug fixes.
︙︙