Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Version 3.31.1 |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | trunk | release | version-3.31.1 |
Files: | files | file ages | folders |
SHA3-256: |
2ab23690d895727c345904fae00963c5 |
User & Date: | drh 2020-01-27 20:02:45.713 |
Context
2020-01-29
| ||
20:19 | Document the byte-order-mark limitation of fts3/4. (check-in: 7e55864b0a user: dan tags: trunk) | |
2020-01-27
| ||
20:02 | Version 3.31.1 (check-in: 2ab23690d8 user: drh tags: trunk, release, version-3.31.1) | |
18:06 | Initial changes for the 3.31.1 patch release. (check-in: 505d43b621 user: drh tags: trunk) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
17 18 19 20 21 22 23 | proc chng {date desc {options {}}} { global nChng aChng xrefChng set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } | | | > > > | 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 | proc chng {date desc {options {}}} { global nChng aChng xrefChng set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } 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 application. Reverting that change in SQLite, at least temporarily, gives developers of misbehaving applications time to fix their code. <li> Fix a typos in the sqlite3ext.h header file that prevented the [sqlite3_stmt_isexplain()] and [sqlite3_value_frombind()] interfaces from being called from [loadable extensions|run-time loadable extensions]. <p><b>Hashes:</b> <li>SQLITE_SOURCE_ID: 2020-01-27 19:55:54 3bfa9cc97da10598521b342961df8f5f68c7388fa117345eeb516eaa837bb4d6 <li>SHA3-256 for sqlite3.c: de465c64f09529429a38cbdf637acce4dfda6897f93e3db3594009e0fed56d27 } {patchagainst 1} chng {2020-01-22 (3.31.0)} { <li>Add support for [generated columns]. <li>Add the [sqlite3_hard_heap_limit64()] interface and the corresponding [PRAGMA hard_heap_limit] command. <li>Enhance the [function_list pragma] to show the number of arguments on each |
︙ | ︙ |
Changes to pages/chronology.in.
︙ | ︙ | |||
27 28 29 30 31 32 33 | # 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 { | | | 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 { 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 bd49a8271d|2019-02-25|Version 3.27.2 |
︙ | ︙ |
Changes to pages/news.in.
︙ | ︙ | |||
13 14 15 16 17 18 19 | } 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%\">" } | | | 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 | } 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 internal layout of data in an internal SQLite data structure, and those details changed in version 3.31.0, breaking the application. |
︙ | ︙ |