Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Version 3.32.0 |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk | release | version-3.32.0 |
| Files: | files | file ages | folders |
| SHA3-256: |
d816b04a78e47782c34dddb0d5ed9d97 |
| User & Date: | drh 2020-05-22 17:48:35 |
Context
|
2020-05-23
| ||
| 02:01 | Typo: iff() should be iif(). check-in: 93257a1a8d user: drh tags: trunk | |
|
2020-05-22
| ||
| 17:48 | Version 3.32.0 check-in: d816b04a78 user: drh tags: trunk, release, version-3.32.0 | |
| 12:21 | Fix typos. check-in: bf4a56342e user: drh tags: trunk | |
Changes
Changes to pages/changes.in.
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
<li> Add the --bom option to the [.excel], [.output], and [.once]
commands.
<li> Enhance the .filectrl command to support the --schema option.
<li> The [UINT collating sequence] extension is automatically loaded
</ol>
<li> The [ESCAPE] clause of a [LIKE] operator now overrides wildcard
characters, so that the behavior now matches what PostgreSQL does.
<li>SQLITE_SOURCE_ID: <i>pending</i>
<li>SHA3-256 for sqlite3.c: <i>pending</i>
}
chng {2020-01-27 (3.31.1)} {
<li> Revert the data layout for an internal-use-only SQLite data structure.
Applications that use SQLite should never reference internal SQLite
data structures, but some do anyhow, and a change to one such
data structure in 3.30.0 broke a popular and widely-deployed
|
| | |
51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 |
<li> Add the --bom option to the [.excel], [.output], and [.once]
commands.
<li> Enhance the .filectrl command to support the --schema option.
<li> The [UINT collating sequence] extension is automatically loaded
</ol>
<li> The [ESCAPE] clause of a [LIKE] operator now overrides wildcard
characters, so that the behavior now matches what PostgreSQL does.
<li>SQLITE_SOURCE_ID: 2020-05-22 17:46:16 5998789c9c744bce92e4cff7636bba800a75574243d6977e1fc8281e360f8d5a
<li>SHA3-256 for sqlite3.c: 33ed868b21b62ce1d0352ed88bdbd9880a42f29046497a222df6459fc32a356f
}
chng {2020-01-27 (3.31.1)} {
<li> Revert the data layout for an internal-use-only SQLite data structure.
Applications that use SQLite should never reference internal SQLite
data structures, but some do anyhow, and a change to one such
data structure in 3.30.0 broke a popular and widely-deployed
|
Changes to pages/chronology.in.
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
# ORDER BY mtime DESC;
#
# A small amount of manual editing and de-duplication followed.
#
# Manually edit the list for each subsequent release.
#
foreach line [split {
xxxxxxxxxx|2020-05-22|Version 3.32.0
3bfa9cc97d|2020-01-27|Version 3.31.1
f6affdd416|2020-01-22|Version 3.31.0
18db032d05|2019-10-11|Version 3.30.1
18db032d05|2019-10-10|Version 3.30.1
c20a353364|2019-10-04|Version 3.30.0
fc82b73eaa|2019-07-10|Version 3.29.0
884b4b7e50|2019-04-16|Version 3.28.0
|
| |
27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 |
# ORDER BY mtime DESC;
#
# A small amount of manual editing and de-duplication followed.
#
# Manually edit the list for each subsequent release.
#
foreach line [split {
5998789c9c|2020-05-22|Version 3.32.0
3bfa9cc97d|2020-01-27|Version 3.31.1
f6affdd416|2020-01-22|Version 3.31.0
18db032d05|2019-10-11|Version 3.30.1
18db032d05|2019-10-10|Version 3.30.1
c20a353364|2019-10-04|Version 3.30.0
fc82b73eaa|2019-07-10|Version 3.29.0
884b4b7e50|2019-04-16|Version 3.28.0
|
Changes to pages/lang_analyze.in.
136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 |
<p>The recommended usage pattern for the [analysis_limit] pragma is
like this:
<codeblock>
PRAGMA analysis_limit=1000;
</codeblock>
<p>The above analysis limit tells the ANALYZE command to start a full scan
of the index as it normally would. But when the number of rows visited
reaches 1000 (or whatever other limit is specified by the pragma), the
ANALYZE command will begin taking actions to stop the scan. If
the left-most column of the index has changed at least once during the
previous 1000 steps, then the analysis stops immediately. But if the
left-most column has always been the same, then ANALYZE skips ahead to
the first entry with a different left-most column and reads an additional
|
| |
136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 |
<p>The recommended usage pattern for the [analysis_limit] pragma is
like this:
<codeblock>
PRAGMA analysis_limit=1000;
</codeblock>
<p>This pragma tells the ANALYZE command to start a full scan
of the index as it normally would. But when the number of rows visited
reaches 1000 (or whatever other limit is specified by the pragma), the
ANALYZE command will begin taking actions to stop the scan. If
the left-most column of the index has changed at least once during the
previous 1000 steps, then the analysis stops immediately. But if the
left-most column has always been the same, then ANALYZE skips ahead to
the first entry with a different left-most column and reads an additional
|