Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
Comment: | Preliminary changes for version 3.25.2. |
---|---|
Downloads: | Tarball | ZIP archive |
Timelines: | family | ancestors | descendants | both | branch-3.25 |
Files: | files | file ages | folders |
SHA3-256: |
e00e728eae40752ee37280b97366515a |
User & Date: | drh 2018-09-25 15:02:04.712 |
Context
2018-09-25
| ||
16:26 | Improvements to the legacy_alter_table pragma documentation. Typo fix in the change log. (check-in: db3facf719 user: drh tags: branch-3.25) | |
15:02 | Preliminary changes for version 3.25.2. (check-in: e00e728eae user: drh tags: branch-3.25) | |
2018-09-24
| ||
14:46 | Clarify the operation of the "weekday" date and time modifier. (check-in: b4b8f35ef1 user: drh tags: branch-3.25) | |
Changes
Changes to pages/changes.in.
︙ | ︙ | |||
17 18 19 20 21 22 23 24 25 26 27 28 29 30 | proc chng {date desc {options {}}} { global nChng aChng xrefChng set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } chng {2018-09-18 (3.25.1)} { <li> Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged. Ticket [https://sqlite.org/src/info/b41031ea2b537237|b41031ea2b537237]. | > > > > > > > > > > > > > > > > > | 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 44 45 46 47 | proc chng {date desc {options {}}} { global nChng aChng xrefChng set aChng($nChng) [list $date $desc $options] set xrefChng($date) $nChng incr nChng } chng {2018-09-25 (3.25.2)} { <li> Add the [PRAGMA legacy_alter_table=ON] command that causes the "ALTER TABLE RENAME" command to behave as it did in SQLite versions 3.24.0 and earlier: references to the renamed table inside the bodies of triggers and views are not updated. This new pragma provides a compatibility work around for older programs that expected the older, wonky behavior of ALTER TABLE RENAME. <li> Fix a problem with the new [window functions] implementation that caused a malfunction when compress expressions involving window functions were used inside of a view. <li> Fixes for various other compiler warnings and minor problems associated with obscure configurations. <p><b>Hashes:</b> <li>SQLITE_SOURCE_ID: <i>pending</i> <li>SHA3-256 for sqlite3.c: <i>pending</i> } {patchagainst 1 patchagainst 2} chng {2018-09-18 (3.25.1)} { <li> Extra sanity checking added to ALTER TABLE in the 3.25.0 release sometimes raises a false-positive when the table being modified has a trigger that updates a virtual table. The false-positive caused the ALTER TABLE to rollback, thus leaving the schema unchanged. Ticket [https://sqlite.org/src/info/b41031ea2b537237|b41031ea2b537237]. |
︙ | ︙ |
Changes to pages/chronology.in.
︙ | ︙ | |||
24 25 26 27 28 29 30 31 32 33 34 35 36 37 | # 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 { 2ac9003de4|2018-09-18|Version 3.25.1 b63af6c3bd|2018-09-15|Version 3.25.0 c7ee083322|2018-06-04|Version 3.24.0 4bb2294022|2018-04-10|Version 3.23.1 736b53f57f|2018-04-02|Version 3.23.0 0c55d17973|2018-01-22|Version 3.22.0 1a584e4999|2017-10-24|Version 3.21.0 | > | 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | # 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|2018-09-25|Version 3.25.2 2ac9003de4|2018-09-18|Version 3.25.1 b63af6c3bd|2018-09-15|Version 3.25.0 c7ee083322|2018-06-04|Version 3.24.0 4bb2294022|2018-04-10|Version 3.23.1 736b53f57f|2018-04-02|Version 3.23.0 0c55d17973|2018-01-22|Version 3.22.0 1a584e4999|2017-10-24|Version 3.21.0 |
︙ | ︙ |
Changes to pages/index.in.
︙ | ︙ | |||
10 11 12 13 14 15 16 | [full-featured SQL|full-featured], [public-domain], SQL database engine. SQLite is the [most used] database engine in the world. <a class="button" href="about.html">More Info</a></p> <hr class="xhr"> <span class="hdrfont">Latest Release: </span> | | | 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 | [full-featured SQL|full-featured], [public-domain], SQL database engine. SQLite is the [most used] database engine in the world. <a class="button" href="about.html">More Info</a></p> <hr class="xhr"> <span class="hdrfont">Latest Release: </span> <a href="releaselog/3_25_2.html">Version 3.25.2</a> ([dateof:3.25.2]). <a class="button" href="download.html">Download</a> <a class="button" href="chronology.html">Prior Releases</a> <div class="mobileonly"> <hr class="xhr"> <h3>Common Links</h3> <tcl>common_links</tcl> |
︙ | ︙ |
Changes to pages/news.in.
︙ | ︙ | |||
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 regsub -all {[Tt]icket #(\d+)} $txt \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt hd_resolve "<blockquote>$txt</blockquote>" hd_puts "<hr width=\"50%\">" } newsitem {2018-09-18} {Release 3.25.1} { SQLite [version 3.25.1] is a patch against version 3.25.0 that contains two one-line fixes for bug that were introduced in version 3.25.0. See the change log for details. Upgrading from 3.25.0 is recommended. } | > > > > > > > > > > > > > > > > | 14 15 16 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 | hd_puts "<h3>$date - $title</h3>" regsub -all "\n( *\n)+" $text "</p>\n\n<p>" txt regsub -all {[Tt]icket #(\d+)} $txt \ {<a href="http://www.sqlite.org/cvstrac/tktview?tn=\1">\0</a>} txt hd_resolve "<blockquote>$txt</blockquote>" hd_puts "<hr width=\"50%\">" } newsitem {2018-09-25} {Release 3.25.2} { SQLite [version 3.25.2] is another patch against 3.25.0 that fixes still more problems associated with the new [window function] feature and the [ALTER TABLE] enhancements. Of particular note is the new [PRAGMA legacy_alter_table=ON] command, which causes the ALTER TABLE RENAME command to behave in the same goofy way that it did before the enhancements found in version 3.25.0 → references to renamed tables that are inside the bodies of triggers and views are not updated. The legacy behavior is arguably a bug, but some programs depend on the older buggy behavior. The 3.25.2 release also contains a fix to [window function] processing for VIEWs. There also a slew of other minor fixes that affect obscure compile-time options. See the [https://sqlite.org/src/timeline?r=branch-3.25|Fossil Timeline] for details. } newsitem {2018-09-18} {Release 3.25.1} { SQLite [version 3.25.1] is a patch against version 3.25.0 that contains two one-line fixes for bug that were introduced in version 3.25.0. See the change log for details. Upgrading from 3.25.0 is recommended. } |
︙ | ︙ |
Changes to pages/pragma.in.
︙ | ︙ | |||
766 767 768 769 770 771 772 773 774 775 776 777 778 779 | <p>^This pragma only operates on the single database specified prior to the pragma name (or on the "main" database if no database is specified.) There is no way to change the journal size limit on all attached databases using a single PRAGMA statement. The size limit must be set separately for each attached database. } Pragma legacy_file_format { <p>^(<b>PRAGMA legacy_file_format; <br>PRAGMA legacy_file_format = <i>boolean</i></b></p> <p>This pragma sets or queries the value of the legacy_file_format flag.)^ ^(When this flag is on, new SQLite databases are created in a file format that is readable and writable by all versions of | > > > > > > > > > > > > > > > > > > > > > | 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 | <p>^This pragma only operates on the single database specified prior to the pragma name (or on the "main" database if no database is specified.) There is no way to change the journal size limit on all attached databases using a single PRAGMA statement. The size limit must be set separately for each attached database. } Pragma legacy_alter_table { <p>^(<b>PRAGMA legacy_alter_table; <br>PRAGMA legacy_alter_table = <i>boolean</i></b></p> <p>This pragma sets or queries the value of the legacy_alter_table flag.)^ ^(When this flag is on, the ALTER TABLE RENAME command does not modify references to the renamed table in the body of triggers and views.)^ This mimics the behavior of of SQLite version 3.24.0 ([dateof:3.24.0]) and earlier. When this flag is off (the default) then the ALTER TABLE RENAME command does update references to the renamed table that occur in the body of triggers and views, as it should. <p>This pragma is provided as a work-around for older programs that contain code that expect the goofy behavior of ALTER TABLE RENAME found in older versions of SQLite. New applications should leave this flag turned off. <p>For compability with older [virtual table] implementations, this flag is turned on temporarily while the [sqlite3_module.xRename] method is being run. The value of this flag is restore after the [sqlite3_module.xRename] method finishes. } Pragma legacy_file_format { <p>^(<b>PRAGMA legacy_file_format; <br>PRAGMA legacy_file_format = <i>boolean</i></b></p> <p>This pragma sets or queries the value of the legacy_file_format flag.)^ ^(When this flag is on, new SQLite databases are created in a file format that is readable and writable by all versions of |
︙ | ︙ |
Changes to pages/vtab.in.
︙ | ︙ | |||
1373 1374 1375 1376 1377 1378 1379 | </codeblock> <p>This method provides notification that the virtual table implementation that the virtual table will be given a new name. If this method returns [SQLITE_OK] then SQLite renames the table. If this method returns an [error code] then the renaming is prevented. | | > > > > > > > > > | 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 | </codeblock> <p>This method provides notification that the virtual table implementation that the virtual table will be given a new name. If this method returns [SQLITE_OK] then SQLite renames the table. If this method returns an [error code] then the renaming is prevented. <p>The xRename method is optional. If omitted, then the virtual table may not be renamed using the ALTER TABLE RENAME command. <p>The [PRAGMA legacy_alter_table=ON] command is run prior to invoking this method, and the prior value for legacy_alter_table is restored after this method finishes. This is necessary for the correct operation of virtual tables that make use of [shadow tables] where the shadow tables must be renamed to match the new virtual table name. If the legacy_alter_format is off, then the xConnect method will be invoked for the virtual table every time the xRename method tries to change the name of the shadow table. <tcl>############################################################# xSavepoint hd_fragment xsavepoint {sqlite3_module.xSavepoint} {xSavepoint}\ xRelease xRollbackTo</tcl> <h2>The xSavepoint, xRelease, and xRollbackTo Methods</h2> <codeblock> |
︙ | ︙ |
Changes to pages/windowfunctions.in.
|
| | | 1 2 3 4 5 6 7 8 | <tcl>hd_keywords {window functions} {window function}</tcl> <title>Window Functions</title> <table_of_contents> <h1>Introduction to Window Functions</h1> <p>A window function is a special SQL function where the input |
︙ | ︙ |