Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Add a news item for the 3.32.0 release. Change the release date to today. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA3-256: |
4e9d9494bbfb89ef78a75e302444b748 |
| User & Date: | drh 2020-05-22 12:12:24 |
Context
|
2020-05-22
| ||
| 12:21 | Fix typos. check-in: bf4a56342e user: drh tags: trunk | |
| 12:12 | Add a news item for the 3.32.0 release. Change the release date to today. check-in: 4e9d9494bb user: drh tags: trunk | |
| 12:05 | Make dbsqlfuzz one of the primary test harnesses for SQLite. check-in: b56e6bd246 user: drh tags: trunk | |
Changes
Changes to pages/changes.in.
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
proc chng {date desc {options {}}} {
global nChng aChng xrefChng
set aChng($nChng) [list $date $desc $options]
set xrefChng($date) $nChng
incr nChng
}
chng {2020-05-29 (3.32.0)} {
<li> Added support for [approximate ANALYZE] using the
[PRAGMA analysis_limit] command.
<li> Added the [bytecode virtual table].
<li> Add the [checksum VFS shim] to the set of run-time loadable
extensions included in the source tree.
<li> Added the [iif() SQL function].
<li> INSERT and UPDATE statements now always apply [column affinity]
|
| |
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 |
proc chng {date desc {options {}}} {
global nChng aChng xrefChng
set aChng($nChng) [list $date $desc $options]
set xrefChng($date) $nChng
incr nChng
}
chng {2020-05-22 (3.32.0)} {
<li> Added support for [approximate ANALYZE] using the
[PRAGMA analysis_limit] command.
<li> Added the [bytecode virtual table].
<li> Add the [checksum VFS shim] to the set of run-time loadable
extensions included in the source tree.
<li> Added the [iif() SQL function].
<li> INSERT and UPDATE statements now always apply [column affinity]
|
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-29|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 {
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
|
Changes to pages/news.in.
12 13 14 15 16 17 18 19 20 21 22 23 24 25 |
{<a href="releaselog/\2_\3_\4.html">\0</a>} title
}
hd_puts "<h3>$date - $title</h3>"
regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt
hd_resolve "<blockquote>$txt</blockquote>"
hd_puts "<hr width=\"50%\">"
}
newsitem {2020-01-27} {Release 3.31.1} {
Applications that use SQLite should only interface with SQLite
through the officially published APIs. Applications should not
depend upon or use the internal data structures of SQLite as those
structures might change from one release to another. However, there
is a popular application that does depend on the details of the
|
> > > > > > > > > > |
12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 |
{<a href="releaselog/\2_\3_\4.html">\0</a>} title
}
hd_puts "<h3>$date - $title</h3>"
regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt
hd_resolve "<blockquote>$txt</blockquote>"
hd_puts "<hr width=\"50%\">"
}
newsitem {2020-05-22} {Release 3.32.0} {
Version 3.32.0 is an ordinary maintenance release of SQLite.
This release features the ability to run an
[approximate ANALYZE] to gather database statistics for
use by the query planner, without having to scan every row
of every index.
See the [version 3.32.0|change log] for additional enhancements
and improvements.
}
newsitem {2020-01-27} {Release 3.31.1} {
Applications that use SQLite should only interface with SQLite
through the officially published APIs. Applications should not
depend upon or use the internal data structures of SQLite as those
structures might change from one release to another. However, there
is a popular application that does depend on the details of the
|