The NetBSD Project

CVS log for pkgsrc/databases/sqlite3-docs/distinfo

[BACK] Up to [] / pkgsrc / databases / sqlite3-docs

Request diff between arbitrary revisions

Default branch: MAIN

Revision 1.132 / (download) - annotate - [select for diffs], Sat Nov 25 21:07:38 2023 UTC (2 weeks, 1 day ago) by adam
Branch: MAIN
Changes since 1.131: +4 -4 lines
Diff to previous 1.131 (colored)

sqlite3: updated to 3.44.2

3.44.1 (2023-11-22):

Change the CLI so that it uses UTF-16 for console I/O on Windows. This enables proper display of unicode text on old Windows7 machines.
Other obscure bug fixes.

3.44.2 (2023-11-24):

Fix a mistake in the CLI that was introduced by the fix (item 15 above) in 3.44.1.
Fix a problem in FTS5 that was discovered during internal fuzz testing only minutes after the 3.44.1 release was tagged.
Fix incomplete assert() statements that the fuzzer discovered the day after the previous release.
Fix a couple of harmless compiler warnings that appeared in debug builds with GCC 16.

Revision 1.131 / (download) - annotate - [select for diffs], Wed Nov 1 20:46:04 2023 UTC (5 weeks, 4 days ago) by adam
Branch: MAIN
Changes since 1.130: +4 -4 lines
Diff to previous 1.130 (colored)

sqlite3: updated to 3.44.0

SQLite Release 3.44.0 On 2023-11-01

Aggregate functions can now include an ORDER BY clause after their last parameter. The arguments to the function are processed in the order specified. This can be important for functions like string_agg() and json_group_array().
Add support for the concat() and concat_ws() scalar SQL functions, compatible with PostgreSQL, SQLServer, and MySQL.
Add support for the string_agg() aggregate SQL function, compatible with PostgreSQL and SQLServer.
New conversion letters on the strftime() SQL function: %e %F %I %k %l %p %P %R %T %u
Add new C-language APIs: sqlite3_get_clientdata() and sqlite3_set_clientdata().
Many errors associated with CREATE TABLE are now raised when the CREATE TABLE statement itself is run, rather than being deferred until the first time the table is actually used.
The PRAGMA integrity_check command now verifies the consistency of the content in various built-in virtual tables using the new xIntegrity method. This works for the FTS3, FTS4, FTS5, RTREE, and GEOPOLY extensions.
The SQLITE_DBCONFIG_DEFENSIVE setting now prevents PRAGMA writable_schema from being turned on. Previously writable_schema could be turned on, but would not actually allow the schema to be writable. Now it simply cannot be turned on.
Tag the built-in FTS3, FTS4, FTS5, RTREE, and GEOPOLY virtual tables as SQLITE_VTAB_INNOCUOUS so that they can be used inside of triggers in high-security deployments.
The PRAGMA case_sensitive_like statement is deprecated, as its use when the schema contains LIKE operators can lead to reports of database corruption by PRAGMA integrity_check.
SQLITE_USE_SEH (Structured Exception Handling) is now enabled by default whenever SQLite is built using the Microsoft C compiler. It can be disabled using -DSQLITE_USE_SEH=0
Query planner optimizations:
In partial index scans, if the WHERE clause implies a constant value for a table column, replace occurrences of that table column with the constant. This increases the likelihood of the partial index being a covering index.
Disable the view-scan optimization (added in version 3.42.0 - item 1c) as it was causing multiple performance regressions. In its place, reduce the estimated row count for DISTINCT subqueries by a factor of 8.
SQLite now performs run-time detection of whether or not the underlying hardware supports "long double" with precision greater than "double" and uses appropriate floating-point routines depending on what it discovered.
The CLI for Windows now defaults to using UTF-8 for both input and output on platforms that support it. The --no-utf8 option is available to disable UTF8 support.

Revision 1.130 / (download) - annotate - [select for diffs], Tue Oct 10 16:16:48 2023 UTC (2 months ago) by adam
Branch: MAIN
Changes since 1.129: +4 -4 lines
Diff to previous 1.129 (colored)

sqlite3: updated to 3.43.2

Changes in this specific patch release, version 3.43.2 (2023-10-10):

Fix a couple of obscure UAF errors and an obscure memory leak.
Omit the use of the sprintf() function from the standard library in the CLI, as this now generates warnings on some platforms.
Avoid conversion of a double into unsigned long long integer, as some platforms do not do such conversions correctly.

Revision 1.129 / (download) - annotate - [select for diffs], Tue Sep 12 19:28:12 2023 UTC (2 months, 4 weeks ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2023Q3-base, pkgsrc-2023Q3
Changes since 1.128: +4 -4 lines
Diff to previous 1.128 (colored)

sqlite3: updated to 3.43.1


Fix a regression in the way that the sum(), avg(), and total() aggregate functions handle infinities.
Fix a bug in the json_array_length() function that occurs when the argument comes directly from json_remove().
Fix the omit-unused-subquery-columns optimization (introduced in in version 3.42.0) so that it works correctly if the subquery is a compound where one arm is DISTINCT and the other is not.
Other minor fixes.

Revision 1.128 / (download) - annotate - [select for diffs], Fri Aug 25 06:48:00 2023 UTC (3 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.127: +4 -4 lines
Diff to previous 1.127 (colored)

databases/sqlite3* devel/lemon: updated to 2.43.0

SQLite Release 3.43.0 On 2023-08-24

Add support for Contentless-Delete FTS5 Indexes. This is a variety of FTS5 full-text search index that omits storing the content that is being indexed while also allowing records to be deleted.
Enhancements to the date and time functions:
Added new time shift modifiers of the form ±YYYY-MM-DD HH:MM:SS.SSS.
Added the timediff() SQL function.
Added the octet_length(X) SQL function.
Added the sqlite3_stmt_explain() API.
Query planner enhancements:
Generalize the LEFT JOIN strength reduction optimization so that it works for RIGHT and FULL JOINs as well. Rename it to OUTER JOIN strength reduction.
Enhance the theorem prover in the OUTER JOIN strength reduction optimization so that it returns fewer false-negatives.
Enhancements to the decimal extension:
New function decimal_pow2(N) returns the N-th power of 2 for integer N between -20000 and +20000.
New function decimal_exp(X) works like decimal(X) except that it returns the result in exponential notation - with a "e+NN" at the end.
If X is a floating-point value, then the decimal(X) function now does a full expansion of that value into its exact decimal equivalent.
Performance enhancements to JSON processing results in a 2x performance improvement for some kinds of processing on large JSON strings.
New makefile target "verify-source" checks to ensure that there are no unintentional changes in the source tree. (Works for canonical source code only - not for precompiled amalgamation tarballs.)
Added the SQLITE_USE_SEH compile-time option that enables Structured Exception Handling on Windows while working with the memory-mapped shm file that is part of WAL mode processing. This option is enabled by default when building on Windows using Makefile.msc.
The VFS for unix now assumes that the nanosleep() system call is available unless compiled with -DHAVE_NANOSLEEP=0.

Revision 1.127 / (download) - annotate - [select for diffs], Wed May 17 12:29:58 2023 UTC (6 months, 3 weeks ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2023Q2-base, pkgsrc-2023Q2
Changes since 1.126: +4 -4 lines
Diff to previous 1.126 (colored)

sqlite3: updated to 3.42.0

SQLite Release 3.42.0 On 2023-05-16

Add the FTS5 secure-delete command. This option causes all forensic traces to be removed from the FTS5 inverted index when content is deleted.
Enhance the JSON SQL functions to support JSON5 extensions.
The SQLITE_CONFIG_LOG and SQLITE_CONFIG_PCACHE_HDRSZ calls to sqlite3_config() are now allowed to occur after sqlite3_initialize().
Query planner improvements:
Enable the "count-of-view" optimization by default.
Avoid computing unused columns in subqueries.
Improvements to the push-down optimization.
Enhancements to the CLI:
Add the --unsafe-testing command-line option. Without this option, some dot-commands (ex: ".testctrl") are now disabled because those commands that are intended for testing only and can cause malfunctions misused.
Allow commands ".log on" and ".log off", even in --safe mode.
"--" as a command-line argument means all subsequent arguments that start with "-" are interpreted as normal non-option argument.
Magic parameters ":inf" and ":nan" bind to floating point literals Infinity and NaN, respectively.
The --utf8 command-line option omits all translation to or from MBCS on the Windows console for interactive sessions, and sets the console code page for UTF-8 I/O during such sessions. The --utf8 option is a no-op on all other platforms.
Add the ability for application-defined SQL functions to have the same name as join keywords: CROSS, FULL, INNER, LEFT, NATURAL, OUTER, or RIGHT.
Enhancements to PRAGMA integrity_check:
Detect and raise an error when a NaN value is stored in a NOT NULL column.
Improved error message output identifies the root page of a b-tree when an error is found within a b-tree.
Allow the session extension to be configured to capture changes from tables that lack an explicit ROWID.
Added the subsecond modifier to the date and time functions.
Negative values passed into sqlite3_sleep() are henceforth interpreted as 0.
The maximum recursion depth for JSON arrays and objects is lowered from 2000 to 1000.
Extended the built-in printf() function so the comma option now works with floating-point conversions in addition to integer conversions.
Miscellaneous bug fixes and performance optimizations

Revision 1.126 / (download) - annotate - [select for diffs], Tue Mar 28 13:01:40 2023 UTC (8 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.125: +4 -4 lines
Diff to previous 1.125 (colored)

sqlite3: updated to 3.41.2

version 3.41.2 (2023-03-22):

Multiple fixes for reads past the end of memory buffers (NB: reads not writes) in the following circumstances:
When processing a corrupt database file using the non-standard SQLITE_ENABLE_STAT4 compile-time option.
In the CLI when the sqlite3_error_offset() routine returns an out-of-range value (see also the fix to sqlite3_error_offset() below).
In the recovery extension.
In FTS3 when processing a corrupt database file.
Fix the sqlite3_error_offset() so that it does not return out-of-range values when reporting errors associated with generated columns.
Multiple fixes in the query optimizer for problems that cause incorrect results for bizarre, fuzzer-generated queries.
Increase the size of the reference counter in the page cache object to 64 bits to ensure that the counter never overflows.
Fix a performance regression caused by a bug fix in patch release 3.41.1.
Fix a few incorrect assert() statements.

Revision 1.125 / (download) - annotate - [select for diffs], Sun Mar 12 10:34:32 2023 UTC (9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2023Q1-base, pkgsrc-2023Q1
Changes since 1.124: +4 -4 lines
Diff to previous 1.124 (colored)

sqlite3: updated to 3.41.1

version 3.41.1 (2023-03-10):

Provide compile-time options -DHAVE_LOG2=0 and -DHAVE_LOG10=0 to enable SQLite to be compiled on systems that omit the standard library functions log2() and log10(), repectively.
Ensure that the datatype for column t1.x in "CREATE TABLE t1 AS SELECT CAST(7 AS INT) AS x;" continues to be INT and is not NUM, for historical compatibility.
Enhance PRAGMA integrity_check to detect when extra bytes appear at the end of an index record.
Fix various obscure bugs reported by the user community. See the timeline of changes for details.

Revision 1.124 / (download) - annotate - [select for diffs], Fri Feb 24 08:34:38 2023 UTC (9 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.123: +4 -4 lines
Diff to previous 1.123 (colored)

sqlite3: updated to 3.41.0

SQLite Release 3.41.0 On 2023-02-21

Query planner improvements:
Make use of indexed expressions within an aggregate query that includes a GROUP BY clause.
The query planner has improved awareness of when an index is a covering index and adjusts predicted runtimes accordingly.
The query planner is more aggressive about using co-routines rather than materializing subqueries and views.
Queries against the built-in table-valued functions json_tree() and json_each() will now usually treat "ORDER BY rowid" as a no-op.
Enhance the ability of the query planner to use indexed expressions even if the expression has been modified by the constant-propagation optimization. (See forum thread 0a539c7.)
Add the built-in unhex() SQL function.
Add the base64 and base85 application-defined functions as an extension and include that extension in the CLI.
Add the sqlite3_stmt_scanstatus_v2() interface. (This interface is only available if SQLite is compiled using SQLITE_ENABLE_STMT_SCANSTATUS.)
In-memory databases created using sqlite3_deserialize() now report their filename as an empty string, not as 'x'.
Changes to the CLI:
Add the new base64() and base85() SQL functions
Enhanced EXPLAIN QUERY PLAN output using the new sqlite3_stmt_scanstatus_v2() interface when compiled using SQLITE_ENABLE_STMT_SCANSTATUS.
The ".scanstats est" command provides query planner estimates in profiles.
The continuation prompt indicates if the input is currently inside of a string literal, identifier literal, comment, trigger definition, etc.
Enhance the --safe command-line option to disallow dangerous SQL functions.
The double-quoted string misfeature is now disabled by default for CLI builds. Legacy use cases can reenable the misfeature at run-time using the ".dbconfig dqs_dml on" and ".dbconfig dqs_ddl on" commands.
Enhance the PRAGMA integrity_check command so that it detects when text strings in a table are equivalent to but not byte-for-byte identical to the same strings in the index.
Enhance the carray table-valued function so that it is able to bind an array of BLOB objects.
Added the sqlite3_is_interrupted() interface.
Long-running calls to sqlite3_prepare() and similar now invoke the progress handler callback and react to sqlite3_interrupt().
The sqlite3_vtab_in_first() and sqlite3_vtab_in_next() functions are enhanced so that they reliably detect if they are invoked on a parameter that was not selected for multi-value IN processing using sqlite3_vtab_in(). They return SQLITE_ERROR instead of SQLITE_MISUSE in this case.
The parser now ignores excess parentheses around a subquery on the right-hand side of an IN operator, so that SQLite now works the same as PostgreSQL in this regard. Formerly, SQLite treated the subquery as an expression with an implied "LIMIT 1".
Added the SQLITE_FCNTL_RESET_CACHE option to the sqlite3_file_control() API.
Makefile improvements:
The new makefile target "sqlite3r.c" builds an amalgamation that includes the recovery extension.
New makefile targets "devtest" and "releasetest" for running a quick developmental test prior to doing a check-in and for doing a full release test, respectively.
Miscellaneous performance enhancements.

Revision 1.123 / (download) - annotate - [select for diffs], Wed Dec 28 22:26:06 2022 UTC (11 months, 1 week ago) by adam
Branch: MAIN
Changes since 1.122: +4 -4 lines
Diff to previous 1.122 (colored)

sqlite3: updated to 3.40.1

3.40.1 (2022-12-28):

Fix the --safe command-line option to the CLI such that it correctly disallows the use of SQL functions like writefile() that can cause harmful side-effects.
Fix a potential infinite loop in the memsys5 alternative memory allocator. This bug was introduced by a performance optimization in version 3.39.0.
Various other obscure fixes.

Revision 1.122 / (download) - annotate - [select for diffs], Thu Nov 17 06:20:44 2022 UTC (12 months, 3 weeks ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q4-base, pkgsrc-2022Q4
Changes since 1.121: +4 -4 lines
Diff to previous 1.121 (colored)

sqlite3: updated to 3.40.0

SQLite Release 3.40.0

Add support for compiling SQLite to WASM and running it in web browsers. NB: The WASM build and its interfaces are considered "beta" and are subject to minor changes if the need arises. We anticipate finalizing the interface for the next release.
Add the recovery extension that might be able to recover some content from a corrupt database file.
Query planner enhancements:
Recognize covering indexes on tables with more than 63 columns where columns beyond the 63rd column are used in the query and/or are referenced by the index.
Extract the values of expressions contained within expression indexes where practical, rather than recomputing the expression.
The NOT NULL and IS NULL operators (and their equivalents) avoid loading the content of large strings and BLOB values from disk.
Avoid materializing a view on which a full scan is performed exactly once. Use and discard the rows of the view as they are computed.
Allow flattening of a subquery that is the right-hand operand of a LEFT JOIN in an aggregate query.
A new typedef named sqlite3_filename is added and used to represent the name of a database file. Various interfaces are modified to use the new typedef instead of "char*". This interface change should be fully backwards compatible, though it might cause (harmless) compiler warnings when rebuilding some legacy applications.
Add the sqlite3_value_encoding() interface.
Security enhancement: SQLITE_DBCONFIG_DEFENSIVE is augmented to prohibit changing the schema_version. The schema_version becomes read-only in defensive mode.
Enhancements to the PRAGMA integrity_check statement:
Columns in non-STRICT tables with TEXT affinity should not contain numeric values.
Columns in non-STRICT tables with NUMERIC affinity should not contain TEXT values that could be converted into numbers.
Verify that the rows of a WITHOUT ROWID table are in the correct order.
Enhance the VACUUM INTO statement so that it honors they PRAGMA synchronous setting.
Enhance the sqlite3_strglob() and sqlite3_strlike() APIs so that they are able to accept NULL pointers for their string parameters and still generate a sensible result.
Provide the new SQLITE_MAX_ALLOCATION_SIZE compile-time option for limiting the size of memory allocations.
Change the algorithm used by SQLite's built-in pseudo-random number generator (PRNG) from RC4 to Chacha20.
Allow two or more indexes to have the same name as long as they are all in separate schemas.
Miscellaneous performance optimizations result in about 1% fewer CPU cycles used on typical workloads.

Revision / (download) - annotate - [select for diffs], Fri Oct 21 19:39:49 2022 UTC (13 months, 2 weeks ago) by bsiegert
Branch: pkgsrc-2022Q3
Changes since 1.120: +4 -4 lines
Diff to previous 1.120 (colored) next main 1.121 (colored)

Pullup ticket #6688 - requested by taca
databases/sqlite3: security fix (for ruby-sqlite3)

Revisions pulled up:
- databases/sqlite3-docs/PLIST                                  1.118
- databases/sqlite3-docs/distinfo                               1.121
- databases/sqlite3-tcl/distinfo                                1.133
- databases/sqlite3/Makefile.common                             1.95
- databases/sqlite3/distinfo                                    1.188
- devel/lemon/distinfo                                          1.62

   Module Name:	pkgsrc
   Committed By:	adam
   Date:		Mon Oct  3 12:27:52 UTC 2022

   Modified Files:
   	pkgsrc/databases/sqlite3: Makefile.common distinfo
   	pkgsrc/databases/sqlite3-docs: PLIST distinfo
   	pkgsrc/databases/sqlite3-tcl: distinfo
   	pkgsrc/devel/lemon: distinfo

   Log Message:
   sqlite3: updated to 3.39.4

   Changes in version 3.39.4 (2022-09-29):

   Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT
   Fix a long-standing problem in the btree balancer that might, in rare cases, cause database corruption if the application uses an application-defined page cache.
   Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE TRIGGER statements if one or more of the statements in the body of the trigger write into shadow tables.
   Fix a possible integer overflow in the size computation for a memory allocation in FTS3.
   Fix a misuse of the sqlite3_set_auxdata() interface in the ICU Extension.

Revision 1.121 / (download) - annotate - [select for diffs], Mon Oct 3 12:27:52 2022 UTC (14 months, 1 week ago) by adam
Branch: MAIN
Changes since 1.120: +4 -4 lines
Diff to previous 1.120 (colored)

sqlite3: updated to 3.39.4

Changes in version 3.39.4 (2022-09-29):

Fix the build on Windows so that it works with -DSQLITE_OMIT_AUTOINIT
Fix a long-standing problem in the btree balancer that might, in rare cases, cause database corruption if the application uses an application-defined page cache.
Enhance SQLITE_DBCONFIG_DEFENSIVE so that it disallows CREATE TRIGGER statements if one or more of the statements in the body of the trigger write into shadow tables.
Fix a possible integer overflow in the size computation for a memory allocation in FTS3.
Fix a misuse of the sqlite3_set_auxdata() interface in the ICU Extension.

Revision 1.120 / (download) - annotate - [select for diffs], Tue Sep 6 18:59:11 2022 UTC (15 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q3-base
Branch point for: pkgsrc-2022Q3
Changes since 1.119: +4 -4 lines
Diff to previous 1.119 (colored)

sqlite3: updated to 3.39.3

Changes in version 3.39.3 (2022-09-05):

Use a statement journal on DML statement affecting two or more database rows if the statement makes use of a SQL functions that might abort. See forum thread 9b9e4716c0d7bbd1.
Use a mutex to protect the PRAGMA temp_store_directory and PRAGMA data_store_directory statements, even though they are deprecated and documented as not being threadsafe. See forum post 719a11e1314d1c70.
Other bug and warning fixes. See the timeline for details.

Revision 1.119 / (download) - annotate - [select for diffs], Fri Jul 22 07:05:55 2022 UTC (16 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.118: +4 -4 lines
Diff to previous 1.118 (colored)

sqlite3: updated to 3.39.2

changes in version 3.39.2 (2022-07-21):

Fix a performance regression in the query planner associated with rearranging the order of FROM clause terms in the presences of a LEFT JOIN.
Apply fixes for CVE-2022-35737, Chromium bugs 1343348 and 1345947, forum post 3607259d3c, and other minor problems discovered by internal testing.

Revision 1.118 / (download) - annotate - [select for diffs], Thu Jul 14 08:05:51 2022 UTC (16 months, 4 weeks ago) by adam
Branch: MAIN
Changes since 1.117: +4 -4 lines
Diff to previous 1.117 (colored)

sqlite3: updated to 3.39.1

Changes in version 3.39.1 (2022-07-13):

Fix an incorrect result from a query that uses a view that contains a compound SELECT in which only one arm contains a RIGHT JOIN and where the view is not the first FROM clause term of the query that contains the view. forum post 174afeae5734d42d.
Fix some harmless compiler warnings.
Fix a long-standing problem with ALTER TABLE RENAME that can only arise if the sqlite3_limit(SQLITE_LIMIT_SQL_LENGTH) is set to a very small value.
Fix a long-standing problem in FTS3 that can only arise when compiled with the SQLITE_ENABLE_FTS3_PARENTHESIS compile-time option.
Fix the build so that is works when the SQLITE_DEBUG and SQLITE_OMIT_WINDOWFUNC compile-time options are both provided at the same time.
Fix the initial-prefix optimization for the REGEXP extension so that it works correctly even if the prefix contains characters that require a 3-byte UTF8 encoding.
Enhance the sqlite_stmt virtual table so that it buffers all of its output.

Revision 1.117 / (download) - annotate - [select for diffs], Fri Jul 1 17:49:39 2022 UTC (17 months, 1 week ago) by adam
Branch: MAIN
Changes since 1.116: +4 -4 lines
Diff to previous 1.116 (colored)

sqlite3: updated to 3.39.0

SQLite Release 3.39.0 On 2022-06-25

Add (long overdue) support for RIGHT and FULL OUTER JOIN.
Add new binary comparison operators IS NOT DISTINCT FROM and IS DISTINCT FROM that are equivalent to IS and IS NOT, respective, for compatibility with PostgreSQL and SQL standards.
Add a new return code (value "3") from the sqlite3_vtab_distinct() interface that indicates a query that has both DISTINCT and ORDER BY clauses.
Added the sqlite3_db_name() interface.
The unix os interface resolves all symbolic links in database filenames to create a canonical name for the database before the file is opened.
Defer materializing views until the materialization is actually needed, thus avoiding unnecessary work if the materialization turns out to never be used.
The HAVING clause of a SELECT statement is now allowed on any aggregate query, even queries that do not have a GROUP BY clause.
Many microoptimizations collectively reduce CPU cycles by about 2.3%.

Revision 1.116 / (download) - annotate - [select for diffs], Sun May 8 08:10:27 2022 UTC (19 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q2-base, pkgsrc-2022Q2
Changes since 1.115: +4 -4 lines
Diff to previous 1.115 (colored)

sqlite3: updated to 3.38.5

3.38.5 (2022-05-06):

Fix a blunder in the CLI of the 3.38.4 release.

Revision 1.115 / (download) - annotate - [select for diffs], Thu May 5 17:26:41 2022 UTC (19 months ago) by adam
Branch: MAIN
Changes since 1.114: +4 -4 lines
Diff to previous 1.114 (colored)

sqlite3: updated to 3.38.4

3.38.4 (2022-05-04):

Fix a byte-code problem in the Bloom filter pull-down optimization added by release 3.38.0 in which an error in the byte code causes the byte code engine to enter an infinite loop when the pull-down optimization encounters a NULL key.

Revision 1.114 / (download) - annotate - [select for diffs], Wed Apr 27 17:12:17 2022 UTC (19 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.113: +4 -4 lines
Diff to previous 1.113 (colored)

sqlite3: updated to 3.38.3

changes in version 3.38.3 (2022-04-27):

Fix a case of the query planner be overly aggressive with optimizing automatic-index and Bloom-filter construction, using inappropriate ON clause terms to restrict the size of the automatic-index or Bloom filter, and resulting in missing rows in the output. Forum thread 0d3200f4f3bcd3a3.
Other minor patches. See the timeline for details.

Revision 1.113 / (download) - annotate - [select for diffs], Mon Mar 28 19:38:27 2022 UTC (20 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.112: +4 -4 lines
Diff to previous 1.112 (colored)

sqlite3: updated to 3.38.2

Additional changes in version 3.38.2 (2022-03-26):

Fix another user-discovered problem with the new Bloom filter optimization that might cause an incorrect answer when doing a LEFT JOIN with a WHERE clause constraint that says that one of the columns on the right table of the LEFT JOIN is NULL. See forum thread 031e262a89b6a9d2.
Other minor patches. See the timeline for details.

Revision 1.112 / (download) - annotate - [select for diffs], Mon Mar 14 10:01:19 2022 UTC (20 months, 4 weeks ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2022Q1-base, pkgsrc-2022Q1
Changes since 1.111: +4 -4 lines
Diff to previous 1.111 (colored)

sqlite3: updated to 3.38.1

3.38.1 (2022-03-12):

Fix problems with the new Bloom filter optimization that might cause some obscure queries to get an incorrect answer.
Fix the localtime modifier of the date and time functions so that it preserves fractional seconds.
Fix the sqlite_offset SQL function so that it works correctly even in corner cases such as when the argument is a virtual column or the column of a view.
Fix row value IN operator constraints on virtual tables so that they work correctly even if the virtual table implementation relies on bytecode to filter rows that do not satisfy the constraint.
Other minor fixes to assert() statements, test cases, and documentation.

Revision 1.111 / (download) - annotate - [select for diffs], Wed Feb 23 17:07:36 2022 UTC (21 months, 2 weeks ago) by adam
Branch: MAIN
Changes since 1.110: +4 -4 lines
Diff to previous 1.110 (colored)

sqlite3: updated to 3.38.0

SQLite Release 3.38.0 On 2022-02-22

Added the -> and ->> operators for easier processing of JSON. The new operators are compatible with MySQL and PostgreSQL.
The JSON functions are now built-ins. It is no longer necessary to use the -DSQLITE_ENABLE_JSON1 compile-time option to enable JSON support. JSON is on by default. Disable the JSON interface using the new -DSQLITE_OMIT_JSON compile-time option.
Enhancements to date and time functions:
Added the unixepoch() function.
Added the auto modifier and the julianday modifier.
Rename the printf() SQL function to format() for better compatibility. The original printf() name is retained as an alias for backwards compatibility.
Added the sqlite3_error_offset() interface, which can sometimes help to localize an SQL error to a specific character in the input SQL text, so that applications can provide better error messages.
Enhanced the interface to virtual tables as follows:
Added the sqlite3_vtab_distinct() interface.
Added the sqlite3_vtab_rhs_value() interface.
Added the sqlite3_vtab_in() interface (and related) to enable a virtual table to process IN operator constraints all at once, rather than processing each value of the right-hand side of the IN operator separately.
CLI enhancements:
Columnar output modes are enhanced to correctly handle tabs and newlines embedded in text.
Added options like "--wrap N", "--wordwrap on", and "--quote" to the columnar output modes.
Added the .mode qbox alias.
The .import command automatically disambiguates column names.
Use the new sqlite3_error_offset() interface to provide better error messages.
Query planner enhancements:
Use a Bloom filter to speed up large analytic queries.
Use a balanced merge tree to evaluate UNION or UNION ALL compound SELECT statements that have an ORDER BY clause.
The ALTER TABLE statement is changed to silently ignores entries in the sqlite_schema table that do not parse when PRAGMA writable_schema=ON.

Revision 1.110 / (download) - annotate - [select for diffs], Fri Jan 7 21:06:28 2022 UTC (23 months ago) by adam
Branch: MAIN
Changes since 1.109: +4 -4 lines
Diff to previous 1.109 (colored)

sqlite3: updated to 3.37.2

Changes in version 3.37.2:

Fix a bug introduced in version 3.35.0 (2021-03-12) that can cause database corruption if a SAVEPOINT is rolled back while in PRAGMA temp_store=MEMORY mode, and other changes are made, and then the outer transaction commits. Check-in 73c2b50211d3ae26
Fix a long-standing problem with ON DELETE CASCADE and ON UPDATE CASCADE in which a cache of the bytecode used to implement the cascading change was not being reset following a local DDL change. Check-in 5232c9777fe4fb13.
Other minor fixes that should not impact production builds.

Revision 1.109 / (download) - annotate - [select for diffs], Thu Dec 30 20:31:51 2021 UTC (23 months, 1 week ago) by adam
Branch: MAIN
Changes since 1.108: +4 -4 lines
Diff to previous 1.108 (colored)

sqlite3: updated to 3.37.1

version 3.37.1

Fix a bug introduced by the UPSERT enhancements of version 3.35.0 that can cause incorrect byte-code to be generated for some obscure but valid SQL, possibly resulting in a NULL-pointer dereference.
Fix an OOB read that can occur in FTS5 when reading corrupt database files.
Improved robustness of the --safe option in the CLI.
Other minor fixes to assert() statements and test cases.

Revision 1.108 / (download) - annotate - [select for diffs], Sun Nov 28 20:48:28 2021 UTC (2 years ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q4-base, pkgsrc-2021Q4
Changes since 1.107: +4 -4 lines
Diff to previous 1.107 (colored)

sqlite3: updated to 3.37.0

SQLite Release 3.37.0 On 2021-11-27

STRICT tables provide a prescriptive style of data type management, for developers who prefer that kind of thing.
When adding columns that contain a CHECK constraint or a generated column containing a NOT NULL constraint, the ALTER TABLE ADD COLUMN now checks new constraints against preexisting rows in the database and will only proceed if no constraints are violated.
Added the PRAGMA table_list statement.
CLI enhancements:
Add the .connection command, allowing the CLI to keep multiple database connections open at the same time.
Add the --safe command-line option that disables dot-commands and SQL statements that might cause side-effects that extend beyond the single database file named on the command-line.
Performance improvements when reading SQL statements that span many lines.
Added the sqlite3_autovacuum_pages() interface.
The sqlite3_deserialize() does not and has never worked for the TEMP database. That limitation is now noted in the documentation.
The query planner now omits ORDER BY clauses on subqueries and views if removing those clauses does not change the semantics of the query.
The generate_series table-valued function extension is modified so that the first parameter ("START") is now required. This is done as a way to demonstrate how to write table-valued functions with required parameters. The legacy behavior is available using the -DZERO_ARGUMENT_GENERATE_SERIES compile-time option.
Added new sqlite3_changes64() and sqlite3_total_changes64() interfaces.
Added the SQLITE_OPEN_EXRESCODE flag option to sqlite3_open_v2().
Use less memory to hold the database schema.

Revision 1.107 / (download) - annotate - [select for diffs], Tue Oct 26 10:10:05 2021 UTC (2 years, 1 month ago) by nia
Branch: MAIN
Changes since 1.106: +2 -2 lines
Diff to previous 1.106 (colored)

databases: Replace RMD160 checksums with BLAKE2s checksums

All checksums have been double-checked against existing RMD160 and
SHA512 hashes

The following distfiles could not be fetched (some may be only fetched

./databases/cstore/distinfo cstore0.2.tar.gz
./databases/cstore/distinfo data4.tar.gz

Revision 1.106 / (download) - annotate - [select for diffs], Thu Oct 7 13:35:51 2021 UTC (2 years, 2 months ago) by nia
Branch: MAIN
Changes since 1.105: +1 -2 lines
Diff to previous 1.105 (colored)

databases: Remove SHA1 distfile hashes

Revision 1.105 / (download) - annotate - [select for diffs], Fri Jun 25 21:21:31 2021 UTC (2 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q3-base, pkgsrc-2021Q3
Changes since 1.104: +5 -5 lines
Diff to previous 1.104 (colored)

sqlite3: updated to 3.36.0

SQLite Release 3.36.0 On 2021-06-18

Improvement to the EXPLAIN QUERY PLAN output to make it easier to understand.
Byte-order marks at the start of a token are skipped as if they were whitespace.
An error is raised on any attempt to access the rowid of a VIEW or subquery. Formerly, the rowid of a VIEW would be indeterminate and often would be NULL. The -DSQLITE_ALLOW_ROWID_IN_VIEW compile-time option is available to restore the legacy behavior for applications that need it.
The sqlite3_deserialize() and sqlite3_serialize() interfaces are now enabled by default. The -DSQLITE_ENABLE_DESERIALIZE compile-time option is no longer required. Instead, there is is a new -DSQLITE_OMIT_DESERIALIZE compile-time option to omit those interfaces.
The "memdb" VFS now allows the same in-memory database to be shared among multiple database connections in the same process as long as the database name begins with "/".
Back out the EXISTS-to-IN optimization (item 8b in the SQLite 3.35.0 change log) as it was found to slow down queries more often than speed them up.
Improve the constant-propagation optimization so that it works on non-join queries.
The REGEXP extension is now included in CLI builds.

Revision 1.104 / (download) - annotate - [select for diffs], Tue Apr 20 06:30:07 2021 UTC (2 years, 7 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q2-base, pkgsrc-2021Q2
Changes since 1.103: +5 -5 lines
Diff to previous 1.103 (colored)

sqlite3: updated to 3.35.5

version 3.35.5:

Fix defects in the new ALTER TABLE DROP COLUMN feature that could corrupt the database file.
Fix an obscure query optimizer problem that might cause an incorrect query result.

Revision 1.103 / (download) - annotate - [select for diffs], Sat Apr 3 06:25:30 2021 UTC (2 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.102: +5 -5 lines
Diff to previous 1.102 (colored)

sqlite3: updated to 3.35.4


Fix a defect in the query planner optimization identified by item 8b above.
Fix a defect in the new RETURNING syntax.
Fix the new RETURNING feature so that it raises an error if one of the terms in the RETURNING clause references a unknown table, instead of silently ignoring that error.
Fix an assertion associated with aggregate function processing that was incorrectly triggered by the push-down optimization.

Revision 1.102 / (download) - annotate - [select for diffs], Tue Mar 30 07:51:16 2021 UTC (2 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.101: +5 -5 lines
Diff to previous 1.101 (colored)

sqlite3: updated to 3.35.3

changes in version 3.35.3

Enhance the OP_OpenDup opcode of the bytecode engine so that it works even if the cursor being duplicated itself came from OP_OpenDup. Fix for ticket bb8a9fd4a9b7fce5. This problem only came to light due to the recent MATERIALIZED hint enhancement.
When materializing correlated common table expressions, do so separately for each use case, as that is required for correctness. This fixes a problem that was introduced by the MATERIALIZED hint enhancement.
Fix a problem in the filename normalizer of the unix VFS.
Fix the "box" output mode in the CLI so that it works with statements that returns one or more rows of zero columns (such as PRAGMA incremental_vacuum). Forum post afbbcb5b72.
Improvements to error messages generated by faulty common table expressions. Forum post aa5a0431c99e.
Fix some incorrect assert() statements.
Fix to the SELECT statement syntax diagram so that the FROM clause syntax is shown correctly. Forum post 9ed02582fe.
Fix the EBCDIC character classifier so that it understands newlines as whitespace. Forum post 58540ce22dcd.
Improvements the xBestIndex method in the implementation of the (unsupported) wholenumber virtual table extension so that it does a better job of convincing the query planner to avoid trying to materialize a table with an infinite number of rows.

Revision 1.101 / (download) - annotate - [select for diffs], Fri Mar 19 06:29:04 2021 UTC (2 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2021Q1-base, pkgsrc-2021Q1
Changes since 1.100: +5 -5 lines
Diff to previous 1.100 (colored)

sqlite3: updated to 3.35.2

Changes in version 3.35.2:

Fix a problem in the appendvfs.c extension that was introduced into version 3.35.0.
Ensure that date/time functions with no arguments (which generate responses that depend on the current time) are treated as non-deterministic functions. Ticket 2c6c8689fb5f3d2f
Fix a problem in the sqldiff utility program having to do with unusual whitespace characters in a virtual table definition.
Limit the new UNION ALL optimization described by item 8c in the 3.35.0 release so that it does not try to make too many new subqueries. See forum thread 140a67d3d2 for details.

Revision 1.100 / (download) - annotate - [select for diffs], Wed Mar 17 06:24:42 2021 UTC (2 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.99: +5 -5 lines
Diff to previous 1.99 (colored)

sqlite3: updated to 3.35.1


Fix a bug in the new DROP COLUMN feature when used on columns that are indexed and that are quoted in the index definition.
Documentation improvements.

Revision 1.99 / (download) - annotate - [select for diffs], Mon Mar 15 14:51:01 2021 UTC (2 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.98: +5 -5 lines
Diff to previous 1.98 (colored)

sqlite3: updated to 3.35.0

SQLite Release 3.35.0 On 2021-03-12

Added built-in SQL math functions(). (Requires the -DSQLITE_ENABLE_MATH_FUNCTIONS compile-time option.)
Added support for ALTER TABLE DROP COLUMN.
Generalize UPSERT:
Allow multiple ON CONFLICT clauses that are evaluated in order,
The final ON CONFLICT clause may omit the conflict target and yet still use DO UPDATE.
Add support for the RETURNING clause on DELETE, INSERT, and UPDATE statements.
Use less memory when running VACUUM on databases containing very large TEXT or BLOB values. It is no longer necessary to hold the entire TEXT or BLOB in memory all at once.
Add support for the MATERIALIZED and NOT MATERIALIZED hints when specifying common table expressions. The default behavior was formerly NOT MATERIALIZED, but is now changed to MATERIALIZED for CTEs that are used more than once.
The SQLITE_DBCONFIG_ENABLE_TRIGGER and SQLITE_DBCONFIG_ENABLE_VIEW settings are modified so that they only control triggers and views in the main database schema or in attached database schemas and not in the TEMP schema. TEMP triggers and views are always allowed.
Query planner/optimizer improvements:
Enhancements to the min/max optimization so that it works better with the IN operator and the OP_SeekScan optimization of the previous release.
Attempt to process EXISTS operators in the WHERE clause as if they were IN operators, in cases where this is a valid transformation and seems likely to improve performance.
Allow UNION ALL sub-queries to be flattened even if the parent query is a join.
Use an index, if appropriate, on IS NOT NULL expressions in the WHERE clause, even if STAT4 is disabled.
Expressions of the form "x IS NULL" or "x IS NOT NULL" might be converted to simply FALSE or TRUE, if "x" is a column that has a "NOT NULL" constraint and is not involved in an outer join.
Avoid checking foreign key constraints on an UPDATE statement if the UPDATE does not modify any columns associated with the foreign key.
Allow WHERE terms to be pushed down into sub-queries that contain window functions, as long as the WHERE term is made up of entirely of constants and copies of expressions found in the PARTITION BY clauses of all window functions in the sub-query.
CLI enhancements:
Enhance the ".stats" command to accept new arguments "stmt" and "vmstep", causing prepare statement statistics and only the virtual-machine step count to be shown, respectively.
Add the ".filectrl data_version" command.
Enhance the ".once" and ".output" commands so that if the destination argument begins with "|" (indicating that output is redirected into a pipe) then the argument does not need to be quoted.
Bug fixes:
Fix a potential NULL pointer dereference when processing a syntactically incorrect SELECT statement with a correlated WHERE clause and a "HAVING 0" clause. (Also fixed in the 3.34.1 patch release.)
Fix a bug in the IN-operator optimization of version 3.33.0 that can cause an incorrect answer.
Fix incorrect answers from the LIKE operator if the pattern ends with "%" and there is an "ESCAPE '_'" clause.

Revision 1.98 / (download) - annotate - [select for diffs], Wed Jan 20 20:34:37 2021 UTC (2 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.97: +5 -5 lines
Diff to previous 1.97 (colored)

sqlite3: updated to 3.34.1

Changes in version 3.34.1:

Fix a potential use-after-free bug when processing a a subquery with both a correlated WHERE clause and a "HAVING 0" clause and where the parent query is an aggregate.
Fix documentation typos
Fix minor problems in extensions.

Revision 1.97 / (download) - annotate - [select for diffs], Wed Dec 2 07:57:19 2020 UTC (3 years ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q4-base, pkgsrc-2020Q4
Changes since 1.96: +5 -5 lines
Diff to previous 1.96 (colored)

sqlite3: updated to 3.34.0

SQLite Release 3.34.0

Added the sqlite3_txn_state() interface for reporting on the current transaction state of the database connection.
Enhance recursive common table expressions to support two or more recursive terms as is done by SQL Server, since this helps make queries against graphs easier to write and faster to execute.
Improved error messages on CHECK constraint failures.
CLI enhancements:
The .read dot-command now accepts a pipeline in addition to a filename.
Added options --data-only and --nosys to the .dump dot-command.
Added the --nosys option to the .schema dot-command.
Table name quoting works correctly for the .import dot-command.
The generate_series(START,END,STEP) table-valued function extension is now built into the CLI.
The .databases dot-command now show the status of each database file as determined by sqlite3_db_readonly() and sqlite3_txn_state().
Added the --tabs command-line option that sets .mode tabs.
The --init option reports an error if the file named as its argument cannot be opened. The --init option also now honors the --bail option.
Query planner improvements:
Improved estimates for the cost of running a DISTINCT operator.
When doing an UPDATE or DELETE using a multi-column index where only a few of the earlier columns of the index are useful for the index lookup, postpone doing the main table seek until after all WHERE clause constraints have been evaluated, in case those constraints can be covered by unused later terms of the index, thus avoiding unnecessary main table seeks.
The new OP_SeekScan opcode is used to improve performance of multi-column index look-ups when later columns are constrained by an IN operator.
The BEGIN IMMEDIATE and BEGIN EXCLUSIVE commands now work even if one or more attached database files are read-only.
Enhanced FTS5 to support trigram indexes.
Improved performance of WAL mode locking primitives in cases where there are hundreds of connections all accessing the same database file at once.
Enhanced the carray() table-valued function to include a single-argument form that is bound using the auxiliary sqlite3_carray_bind() interface.
The substr() SQL function can now also be called "substring()" for compatibility with SQL Server.
The syntax diagrams are now implemented as Pikchr scripts and rendered as SVG for improved legibility and ease of maintenance.

Revision 1.96 / (download) - annotate - [select for diffs], Wed Aug 19 05:48:37 2020 UTC (3 years, 3 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q3-base, pkgsrc-2020Q3
Changes since 1.95: +5 -5 lines
Diff to previous 1.95 (colored)

sqlite3: updated to 3.33.0

SQLite Release 3.33.0

Support for UPDATE FROM following the PostgreSQL syntax.
Increase the maximum size of database files to 281 TB.
Extended the PRAGMA integrity_check statement so that it can optionally be limited to verifying just a single table and its indexes, rather than the entire database file.
Added the decimal extension for doing arbitrary-precision decimal arithmetic.
Enhancements to the ieee754 extension for working with IEEE 754 binary64 numbers.
CLI enhancements:
Added four new output modes: "box", "json", "markdown", and "table".
The "column" output mode automatically expands columns to contain the longest output row and automatically turns ".header" on if it has not been previously set.
The "quote" output mode honors ".separator"
The decimal extension and the ieee754 extension are built-in to the CLI
Query planner improvements:
Add the ability to find a full-index-scan query plan for queries using INDEXED BY which previously would fail with "no query solution".
Do a better job of detecting missing, incomplete, and/or dodgy sqlite_stat1 data and generates good query plans in spite of the misinformation.
Improved performance of queries like "SELECT min(x) FROM t WHERE y IN (?,?,?)" assuming an index on t(x,y).
In WAL mode, if a writer crashes and leaves the shm file in an inconsistent state, subsequent transactions are now able to recover the shm file even if there are active read transactions. Before this enhancement, shm file recovery that scenario would result in an SQLITE_PROTOCOL error.

Revision 1.95 / (download) - annotate - [select for diffs], Fri Jun 19 07:31:08 2020 UTC (3 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q2-base, pkgsrc-2020Q2
Changes since 1.94: +5 -5 lines
Diff to previous 1.94 (colored)

sqlite3: updated to 3.32.3

Various minor bug fixes

Revision 1.94 / (download) - annotate - [select for diffs], Fri Jun 5 07:48:07 2020 UTC (3 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.93: +5 -5 lines
Diff to previous 1.93 (colored)

sqlite3: updated to 3.32.2

Fix a long-standing bug in the byte-code engine that can cause a COMMIT command report as success when in fact it failed to commit.

Revision 1.93 / (download) - annotate - [select for diffs], Tue May 26 12:50:52 2020 UTC (3 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.92: +5 -5 lines
Diff to previous 1.92 (colored)

sqlite3: updated to 3.32.1

Changes in version 3.32.1:

Fix two long-standing bugs that allow malicious SQL statements to crash the process that is running SQLite. These bugs were announced by a third-party approximately 24 hours after the 3.32.0 release but are not specific to the 3.32.0 release.

Other minor compiler-warning fixes and whatnot.

Revision 1.92 / (download) - annotate - [select for diffs], Sat May 23 07:38:01 2020 UTC (3 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.91: +5 -5 lines
Diff to previous 1.91 (colored)

sqlite3: updated to 3.32.0

SQLite Release 3.32.0:

Added support for approximate ANALYZE using the PRAGMA analysis_limit command.
Added the bytecode virtual table.
Add the checksum VFS shim to the set of run-time loadable extensions included in the source tree.
Added the iif() SQL function.
INSERT and UPDATE statements now always apply column affinity before computing CHECK constraints. This bug fix could, in theory, cause problems for legacy databases with unorthodox CHECK constraints the require the input type for an INSERT is different from the declared column type. See ticket 86ba67afafded936 for more information.
Added the sqlite3_create_filename(), sqlite3_free_filename(), and sqlite3_database_file_object() interfaces to better support of VFS shim implementations.
Increase the default upper bound on the number of parameters from 999 to 32766.
Added code for the UINT collating sequence as an optional loadable extension.
Enhancements to the CLI:
Add options to the .import command: --csv, --ascii, --skip
The .dump command now accepts multiple LIKE-pattern arguments and outputs the union of all matching tables.
Add the .oom command in debugging builds
Add the --bom option to the .excel, .output, and .once commands.
Enhance the .filectrl command to support the --schema option.
The UINT collating sequence extension is automatically loaded
The ESCAPE clause of a LIKE operator now overrides wildcard characters, so that the behavior now matches what PostgreSQL does.

Revision 1.91 / (download) - annotate - [select for diffs], Wed Jan 29 08:33:12 2020 UTC (3 years, 10 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2020Q1-base, pkgsrc-2020Q1
Changes since 1.90: +5 -5 lines
Diff to previous 1.90 (colored)

sqlite3: updated to 3.31.1

SQLite Release 3.31.1:

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.
Fix a typos in the sqlite3ext.h header file that prevented the sqlite3_stmt_isexplain() and sqlite3_value_frombind() interfaces from being called from run-time loadable extensions.

Revision 1.90 / (download) - annotate - [select for diffs], Sun Jan 26 09:05:19 2020 UTC (3 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.89: +5 -5 lines
Diff to previous 1.89 (colored)

sqlite3: updated to 3.31.0

SQLite Release 3.31.0:

Add support for generated columns.
Add the sqlite3_hard_heap_limit64() interface and the corresponding PRAGMA hard_heap_limit command.
Enhance the function_list pragma to show the number of arguments on each function, the type of function (scalar, aggregate, window), and the function property flags SQLITE_DETERMINISTIC, SQLITE_DIRECTONLY, SQLITE_INNOCUOUS, and/or SQLITE_SUBTYPE.
Add the aggregated mode feature to the DBSTAT virtual table.
Add the SQLITE_OPEN_NOFOLLOW option to sqlite3_open_v2() that prevents SQLite from opening symbolic links.
Added the "#-N" array notation for JSON function path arguments.
Added the SQLITE_DBCONFIG_TRUSTED_SCHEMA connection setting which is also controllable via the new trusted_schema pragma and at compile-time using the -DSQLITE_TRUSTED_SCHEMA compile-time option.
Added APIs sqlite3_filename_database(), sqlite3_filename_journal(), and sqlite3_filename_wal() which are useful for specialized extensions.
Add the sqlite3_uri_key() interface.
Upgraded the sqlite3_uri_parameter() function so that it works with the rollback journal or WAL filename in addition to the database filename.
Provide the ability to tag application-defined SQL functions with new properties SQLITE_INNOCUOUS or SQLITE_DIRECTONLY.
Add new verbs to sqlite3_vtab_config() so that the xConnect method of virtual tables can declare the virtual table as SQLITE_VTAB_INNOCUOUS or SQLITE_VTAB_DIRECTONLY.
Faster response to sqlite3_interrupt().
Added the uuid.c extension module implementing functions for processing RFC-4122 UUIDs.
The lookaside memory allocator is enhanced to support two separate memory pools with different sized allocations in each pool. This allows more memory allocations to be covered by lookaside while at the same time reducing the heap memory usage to 48KB per connection, down from 120KB.
The legacy_file_format pragma is deactivated. It is now a no-op. In its place, the SQLITE_DBCONFIG_LEGACY_FILE_FORMAT option to sqlite3_db_config() is provided. The legacy_file_format pragma is deactivated because (1) it is rarely useful and (2) it is incompatible with VACUUM in schemas that have tables with both generated columns and descending indexes.

Revision 1.89 / (download) - annotate - [select for diffs], Fri Oct 11 15:37:09 2019 UTC (4 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q4-base, pkgsrc-2019Q4
Changes since 1.88: +5 -5 lines
Diff to previous 1.88 (colored)

sqlite3: updated to 3.30.1

SQLite Release 3.30.1:
Fix a bug in the query flattener that might cause a segfault for nested queries that use the new FILTER clause on aggregate functions.
Cherrypick fixes for other obscure problems found since the 3.30.0 release.

Revision 1.88 / (download) - annotate - [select for diffs], Sat Oct 5 08:03:55 2019 UTC (4 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.87: +5 -5 lines
Diff to previous 1.87 (colored)

sqlite3: updated to 3.30.0

SQLite Release 3.30.0

Add support for the FILTER clause on aggregate functions.
Add support for the NULLS FIRST and NULLS LAST syntax in ORDER BY clauses.
The index_info and index_xinfo pragmas are enhanced to provide information about the on-disk representation of WITHOUT ROWID tables.
Add the sqlite3_drop_modules() interface, allowing applications to disable automatically loaded virtual tables that they do not need.
Improvements to the .recover dot-command in the CLI so that it recovers more content from corrupt database files.
Enhance the RBU extension to support indexes on expressions.
Change the schema parser so that it will error out if any of the type, name, and tbl_name columns of the sqlite_master table have been corrupted and the database connection is not in writable_schema mode.
The PRAGMA function_list, PRAGMA module_list, and PRAGMA pragma_list commands are now enabled in all builds by default. Disable them using -DSQLITE_OMIT_INTROSPECTION_PRAGMAS.
Add the SQLITE_DBCONFIG_ENABLE_VIEW option for sqlite3_db_config().
Added the TCL Interface config method in order to be able to disable SQLITE_DBCONFIG_ENABLE_VIEW as well as control other sqlite3_db_config() options from TCL.
Added the SQLITE_DIRECTONLY flag for application-defined SQL functions to prevent those functions from being used inside triggers and views.
The legacy SQLITE_ENABLE_STAT3 compile-time option is now a no-op.

Revision 1.87 / (download) - annotate - [select for diffs], Fri Jul 12 10:04:27 2019 UTC (4 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q3-base, pkgsrc-2019Q3
Changes since 1.86: +5 -5 lines
Diff to previous 1.86 (colored)

sqlite3: updated to 3.29.0

SQLite Release 3.29.0:
Added the SQLITE_DBCONFIG_DQS_DML and SQLITE_DBCONFIG_DQS_DDL actions to sqlite3_db_config() for activating and deactivating the double-quoted string literal misfeature. Both default to "on" for legacy compatibility, but developers are encouraged to turn them "off", perhaps using the -DSQLITE_DQS=0 compile-time option.
-DSQLITE_DQS=0 is now a recommended compile-time option.

Improvements to the query planner:
Improved optimization of AND and OR operators when one or the other operand is a constant.
Enhancements to the LIKE optimization for cases when the left-hand side column has numeric affinity.
Added the "sqlite_dbdata" virtual table for extracting raw low-level content from an SQLite database, even a database that is corrupt.

Enhancements to the CLI:
Add the ".recover" command which tries to recover as much content as possible from a corrupt database file.
Add the ".filectrl" command useful for testing.
Add the long-standing ".testctrl" command to the ".help" menu.
Added the ".dbconfig" command

Revision 1.86 / (download) - annotate - [select for diffs], Thu Apr 18 10:10:03 2019 UTC (4 years, 7 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q2-base, pkgsrc-2019Q2
Changes since 1.85: +5 -5 lines
Diff to previous 1.85 (colored)

sqlite3: updated to 3.28.0

SQLite Release 3.28.0:

Enhanced window functions:
Add support the EXCLUDE clause.
Add support for window chaining.
Add support for GROUPS frames.
Add support for "<expr> PRECEDING" and "<expr> FOLLOWING" boundaries in RANGE frames.
Added the new sqlite3_stmt_isexplain(S) interface for determining whether or not a prepared statement is an EXPLAIN.
Enhanced VACUUM INTO so that it works for read-only databases.
New query optimizations:
Enable the LIKE optimization for cases when the ESCAPE keyword is present and PRAGMA case_sensitive_like is on.
In queries that are driven by a partial index, avoid unnecessary tests of the constraint named in the WHERE clause of the partial index, since we know that constraint must always be true.
Enhancements to the TCL Interface:
Added the -returntype option to the function method.
Added the new bind_fallback method.
Enhancements to the CLI:
Added support for bound parameters and the .parameter command.
Fix the readfile() function so that it returns an empty BLOB rather than throwing an out-of-memory error when reading an empty file.
Fix the writefile() function so that when it creates new directories along the path of a new file, it gives them umask permissions rather than the same permissions as the file.
Change --update option in the .archive command so that it skips files that are already in the archive and are unchanged. Add the new --insert option that works like --update used to work.
Added the fossildelta.c extension that can create, apply, and deconstruct the Fossil DVCS file delta format that is used by the RBU extension.
Added the SQLITE_DBCONFIG_WRITABLE_SCHEMA verb for the sqlite3_db_config() interface, that does the same work as PRAGMA writable_schema without using the SQL parser.
Added the sqlite3_value_frombind() API for determining if the argument to an SQL function is from a bound parameter.
Security and compatibilities enhancements to fts3_tokenizer():
The fts3_tokenizer() function always returns NULL unless either the legacy application-defined FTS3 tokenizers interface are enabled using the sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER) setting, or unless the first argument to fts3_tokenizer() is a bound parameter.
The two-argument version of fts3_tokenizer() accepts a pointer to the tokenizer method object even without the sqlite3_db_config(SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER) setting if the second argument is a bound parameter
Improved robustness against corrupt database files.
Miscellaneous performance enhancements

Revision 1.85 / (download) - annotate - [select for diffs], Mon Feb 25 18:04:30 2019 UTC (4 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2019Q1-base, pkgsrc-2019Q1
Changes since 1.84: +5 -5 lines
Diff to previous 1.84 (colored)

sqlite3: updated to 3.27.2

SQLite Release 3.27.2:
Fix a bug in the IN operator that was introduced by an attempted optimization in version 3.27.0.
Fix a bug causing a crash when a window function is misused.
Fix various documentation typos

Revision 1.84 / (download) - annotate - [select for diffs], Mon Feb 11 10:45:20 2019 UTC (4 years, 9 months ago) by adam
Branch: MAIN
Changes since 1.83: +5 -5 lines
Diff to previous 1.83 (colored)

sqlite3: updated to 3.27.1

SQLite Release 3.27.1:
Fix a bug in the query optimizer: an adverse interaction between the OR optimization and the optimization that tries to use values read directly from an expression index instead of recomputing the expression.

Changes carried forward from version 3.27.0:
Added the VACUUM INTO command
Issue an SQLITE_WARNING message on the error log if a double-quoted string literal is used.
The sqlite3_normalized_sql() interface works on any prepared statement created using sqlite3_prepare_v2() or sqlite3_prepare_v3(). It is no longer necessary to use sqlite3_prepare_v3() with SQLITE_PREPARE_NORMALIZE in order to use sqlite3_normalized_sql().
Added the remove_diacritics=2 option to FTS3 and FTS5.
Added the SQLITE_PREPARE_NO_VTAB option to sqlite3_prepare_v3(). Use that option to prevent circular references to shadow tables from causing resource leaks.
Enhancements to the sqlite3_deserialize() interface:
Add the SQLITE_FCNTL_SIZE_LIMIT file-control for setting an upper bound on the size of the in-memory database created by sqlite3_deserialize. The default upper bound is 1GiB, or whatever alternative value is specified by sqlite3_config(SQLITE_CONFIG_MEMDB_MAXSIZE) and/or SQLITE_MEMDB_DEFAULT_MAXSIZE.
Honor the SQLITE_DESERIALIZE_READONLY flag, which was previously described in the documentation, but was previously a no-op.
Enhance the "deserialize" command of the TCL Interface to give it new "--maxsize N" and "--readonly BOOLEAN" options.
Enhancements to the CLI, mostly to support testing and debugging of the SQLite library itself:
Add support for ".open --hexdb". The "dbtotxt" utility program used to generate the text for the "hexdb" is added to the source tree.
Add support for the "--maxsize N" option on ".open --deserialize".
Add the "--memtrace" command-line option, to show all memory allocations and deallocations.
Add the ".eqp trace" option on builds with SQLITE_DEBUG, to enable bytecode program listing with indentation and PRAGMA vdbe_trace all in one step.
Add the ".progress" command for accessing the sqlite3_progress_handler() interface.
Add the "--async" option to the ".backup" command.
Add options "--expanded", "--normalized", "--plain", "--profile", "--row", "--stmt", and "--close" to the ".trace" command.
Increased robustness against malicious SQL that is run against a maliciously corrupted database.

Bug fixes:
Do not use a partial index to do a table scan on an IN operator.
Fix the query flattener so that it works on queries that contain subqueries that use window functions.
Ensure that ALTER TABLE modifies table and column names embedded in WITH clauses that are part of views and triggers.
Fix a parser bug that prevented the use of parentheses around table-valued functions.
Fix a problem with the OR optimization on indexes on expressions.
Fix a problem with the LEFT JOIN strength reduction optimization in which the optimization was being applied inappropriately due to an IS NOT NULL operator.
Fix the REPLACE command so that it is no longer able to sneak a NULL value into a NOT NULL column even if the NOT NULL column has a default value of NULL.
Fix a problem with the use of window functions used within correlated subqueries.
Fix the ALTER TABLE RENAME COLUMN command so that it works for tables that have redundant UNIQUE constraints.
Fix a bug that caused zeroblob values to be truncated when inserted into a table that uses an expression index.

Revision 1.83 / (download) - annotate - [select for diffs], Tue Dec 4 12:03:53 2018 UTC (5 years ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q4-base, pkgsrc-2018Q4
Changes since 1.82: +5 -5 lines
Diff to previous 1.82 (colored)

sqlite3: updated to 3.26.0

SQLite Release 3.26.0:

Optimization: When doing an UPDATE on a table with indexes on expressions, do not update the expression indexes if they do not refer to any of the columns of the table being updated.
Allow the xBestIndex() method of virtual table implementations to return SQLITE_CONSTRAINT to indicate that the proposed query plan is unusable and should not be given further consideration.
Added the SQLITE_DBCONFIG_DEFENSIVE option which disables the ability to create corrupt database files using ordinary SQL.
Added support for read-only shadow tables when the SQLITE_DBCONFIG_DEFENSIVE option is enabled.
Added the PRAGMA legacy_alter_table command, which if enabled causes the ALTER TABLE command to behave like older version of SQLite (prior to version 3.25.0) for compatibility.
Added PRAGMA table_xinfo that works just like PRAGMA table_info except that it also shows hidden columns in virtual tables.
Added the explain virtual table as a run-time loadable extension.
Add a limit counter to the query planner to prevent excessive sqlite3_prepare() times for certain pathological SQL inputs.
Added support for the sqlite3_normalized_sql() interface, when compiling with SQLITE_ENABLE_NORMALIZE.
Enhanced triggers so that they can use table-valued functions that exist in schemas other than the schema where the trigger is defined.
Enhancements to the CLI:
- Improvements to the ".help" command.
- The SQLITE_HISTORY environment variable, if it exists, specifies the name of the command-line editing history file
- The --deserialize option associated with opening a new database cause the database file to be read into memory and accessed using the sqlite3_deserialize() API. This simplifies running tests on a database without modifying the file on disk.
Enhancements to the geopoly extension:
- Aways stores polygons using the binary format, which is faster and uses less space.
- Added the geopoly_regular() function.
- Added the geopoly_ccw() function.
Enhancements to the session extension:
- Added the sqlite3changeset_start_v2() interface and the SQLITE_CHANGESETSTART_INVERT flag.
- Added the changesetfuzz.c test-case generator utility.

Revision 1.82 / (download) - annotate - [select for diffs], Mon Nov 19 16:21:19 2018 UTC (5 years ago) by adam
Branch: MAIN
Changes since 1.81: +5 -5 lines
Diff to previous 1.81 (colored)

sqlite3-docs: updated to 3.25.3 (now available)

Revision 1.81 / (download) - annotate - [select for diffs], Mon Oct 1 08:02:37 2018 UTC (5 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.80: +5 -5 lines
Diff to previous 1.80 (colored)

sqlite3: updated to 3.25.2

SQLite Release 3.25.2:
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.
Fix a problem with the new window functions implementation that caused a malfunction when complicated expressions involving window functions were used inside of a view.
Fixes for various other compiler warnings and minor problems associated with obscure configurations.

Revision 1.80 / (download) - annotate - [select for diffs], Wed Sep 19 09:38:08 2018 UTC (5 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q3-base, pkgsrc-2018Q3
Changes since 1.79: +5 -5 lines
Diff to previous 1.79 (colored)

sqlite3: updated to 3.25.1

SQLite Release 3.25.1:

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.
The fix in the 3.25.0 release for the endless-loop in the byte-code associated with the ORDER BY LIMIT optimization did not work for some queries involving window functions. An additional correction is required.

Revision 1.79 / (download) - annotate - [select for diffs], Mon Sep 17 16:14:07 2018 UTC (5 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.78: +5 -5 lines
Diff to previous 1.78 (colored)

sqlite3: updated to 3.25.0

SQLite Release 3.25.0:

Add support for window functions
Enhancements the ALTER TABLE command:
- Add support for renaming columns within a table using ALTER TABLE table RENAME COLUMN oldname TO newname.
- Fix table rename feature so that it also updates references to the renamed table in triggers and views.
Query optimizer improvements:
- Avoid unnecessary loads of columns in an aggregate query that are not within an aggregate function and that are not part of the GROUP BY clause.
- The IN-early-out optimization: When doing a look-up on a multi-column index and an IN operator is used on a column other than the left-most column, then if no rows match against the first IN value, check to make sure there exist rows that match the columns to the right before continuing with the next IN value.
- Use the transitive property to try to propagate constant values within the WHERE clause. For example, convert "a=99 AND b=a" into "a=99 AND b=99".
Use a separate mutex on every inode in the unix VFS, rather than a single mutex shared among them all, for slightly better concurrency in multi-threaded environments.
Enhance the PRAGMA integrity_check command for improved detection of problems on the page freelist.
Output infinity as 1e999 in the ".dump" command of the command-line shell.
Added the SQLITE_FCNTL_DATA_VERSION file-control.
Added the Geopoly module

Bug fixes:
The ORDER BY LIMIT optimization might have caused an infinite loop in the byte code of the prepared statement under very obscure circumstances, due to a confluence of minor defects in the query optimizer.
On an UPSERT when the order of constraint checks is rearranged, ensure that the affinity transformations on the inserted content occur before any of the constraint checks.
Avoid using a prepared statement for ".stats on" command of the CLI after it has been closed by the ".eqp full" logicc.
The LIKE optimization was generating incorrect byte-code and hence getting the wrong answer if the left-hand operand has numeric affinity and the right-hand-side pattern is '/%' or if the pattern begins with the ESCAPE character.

Revision 1.78 / (download) - annotate - [select for diffs], Thu Jun 7 07:36:49 2018 UTC (5 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q2-base, pkgsrc-2018Q2
Changes since 1.77: +5 -5 lines
Diff to previous 1.77 (colored)

sqlite3: updated to 3.24.0

SQLite Release 3.24.0:
Add support for PostgreSQL-style UPSERT.
Add support for auxiliary columns in r-tree tables.
Add C-language APIs for discovering SQL keywords used by SQLite: sqlite3_keyword_count(), sqlite3_keyword_name(), and sqlite3_keyword_check().
Add C-language APIs for dynamic strings based on the sqlite3_str object.
Enhance ALTER TABLE so that it recognizes "true" and "false" as valid arguments to DEFAULT.
Add the sorter-reference optimization as a compile-time option. Only available if compiled with SQLITE_ENABLE_SORTER_REFERENCES.
Improve the format of the EXPLAIN QUERY PLAN raw output, so that it gives better information about the query plan and about the relationships between the various components of the plan.
Added the SQLITE_DBCONFIG_RESET_DATABASE option to the sqlite3_db_config() API.
CLI Enhancements:

Automatically intercepts the raw EXPLAIN QUERY PLAN output and reformats it into an ASCII-art graph.
Lines that begin with "#" and that are not in the middle of an SQL statement are interpreted as comments.
Added the --append option to the ".backup" command.
Added the ".dbconfig" command.

UPDATE avoids unnecessary low-level disk writes when the contents of the database file do not actually change. For example, "UPDATE t1 SET x=25 WHERE y=?" generates no extra disk I/O if the value in column x is already 25. Similarly, when doing UPDATE on records that span multiple pages, only the subset of pages that actually change are written to disk. This is a low-level performance optimization only and does not affect the behavior of TRIGGERs or other higher level SQL structures.
Queries that use ORDER BY and LIMIT now try to avoid computing rows that cannot possibly come in under the LIMIT. This can greatly improve performance of ORDER BY LIMIT queries, especially when the LIMIT is small relative to the number of unrestricted output rows.
The OR optimization is allowed to proceed even if the OR expression has also been converted into an IN expression. Uses of the OR optimization are now also more clearly shown in the EXPLAIN QUERY PLAN output.
The query planner is more aggressive about using automatic indexes for views and subqueries for which it is not possible to create a persistent index.
Make use of the one-pass UPDATE and DELETE query plans in the R-Tree extension where appropriate.
Performance improvements in the LEMON-generated parser.
Bug fixes:

For the right-hand table of a LEFT JOIN, compute the values of expressions directly rather than loading precomputed values out of an expression index as the expression index might not contain the correct value.
Do not attempt to use terms from the WHERE clause to enable indexed lookup of the right-hand table of a LEFT JOIN.
Fix a memory leak that can occur following a failure to open error in the CSV virtual table
Fix a long-standing problem wherein a corrupt schema on the sqlite_sequence table used by AUTOINCREMENT can lead to a crash.
Fix the json_each() function so that it returns valid results on its "fullkey" column when the input is a simple value rather than an array or object.

Revision 1.77 / (download) - annotate - [select for diffs], Thu Apr 12 10:21:38 2018 UTC (5 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.76: +5 -5 lines
Diff to previous 1.76 (colored)

sqlite: updated to 3.23.1

SQLite Release 3.23.1:
Fix two problems in the new LEFT JOIN strength reduction optimization.
Fix misbehavior of the FTS5 xBestIndex method.
Fix a harmless reference to an uninitialized virtual machine register.
Fix the CLI so that it builds with -DSQLITE_UNTESTABLE
Fix the eval.c extension so that it works with PRAGMA empty_result_callbacks=ON.
Fix the generate_series virtual table so that it correctly returns no rows if any of its constraints are NULL.
Performance enhancements in the parser.

Revision 1.76 / (download) - annotate - [select for diffs], Tue Apr 3 19:58:19 2018 UTC (5 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.75: +5 -5 lines
Diff to previous 1.75 (colored)

sqlite3: updated to 3.23.0

SQLite Release 3.23.0:

Add the sqlite3_serialize() and sqlite3_deserialize() interfaces when the SQLITE_ENABLE_DESERIALIZE compile-time option is used.
Recognize TRUE and FALSE as constants. (For compatibility, if there exist columns named "true" or "false", then the identifiers refer to the columns rather than Boolean constants.)
Support operators IS TRUE, IS FALSE, IS NOT TRUE, and IS NOT FALSE.
Added the SQLITE_DBSTATUS_CACHE_SPILL option to sqlite3_db_status() for reporting the number of cache spills that have occurred.
The "alternate-form-2" flag ("!") on the built-in printf implementation now causes string substitutions to measure the width and precision in characters instead of bytes.
If the xColumn method in a virtual table implementation returns an error message using sqlite3_result_error() then give that error message preference over internally-generated messages.
Added the -A command-line option to the CLI to make it easier to manage SQLite Archive files.
Add support for INSERT OR REPLACE, INSERT OR IGNORE, and UPDATE OR REPLACE in the Zipfile virtual table.
Enhance the sqlite3changeset_apply() interface so that it is hardened against attacks from deliberately corrupted changeset objects.
Added the sqlite3_normalize() extension function.

Query optimizer enhancements:
Improve the omit-left-join optimization so that it works in cases where the right-hand table is UNIQUE but not necessarily NOT NULL.
Improve the push-down optimization so that it works for many LEFT JOINs.
Add the LEFT JOIN strength reduction optimization that converts a LEFT JOIN into an ordinary JOIN if there exist terms in the WHERE clause that would prevent the extra all-NULL row of the LEFT JOIN from appearing in the output set.
Avoid unnecessary writes to the sqlite_sequence table when an AUTOINCREMENT table is updated with an rowid that is less than the maximum.

Bug fixes:
Fix the parser to accept valid row value syntax.
Fix the query planner so that it takes into account dependencies in the arguments to table-valued functions in subexpressions in the WHERE clause.
Fix incorrect result with complex OR-connected WHERE and STAT4.
Fix potential corruption in indexes on expressions due to automatic datatype conversions.
Assertion fault in FTS4.
Incorrect result on the less-than operator in row values.
Always interpret non-zero floating-point values as TRUE, even if the integer part is zero.
Fix an issue in the fsdir(PATH) table-valued function to the fileio.c extension, that caused a segfault if the fsdir() table was used as the inner table of a join.
Issue an error rather instead of an assertion-fault or null-pointer dereference when the sqlite_master table is corrupted so that the sqlite_sequence table root page is really a btree-index page.
Fix the ANALYZE command so that it computes statistics on tables whose names begin with "sqlite".

Additional fixes for issues detected by OSSFuzz:
Fix a possible infinite loop on VACUUM for corrupt database files.
Disallow parameters in the WITH clause of triggers and views.
Fix a potential memory leak in row value processing.
Improve the performance of the replace() SQL function for cases where there are many substitutions on megabyte-sized strings, in an attempt to avoid OSSFuzz timeouts during testing.
Provide an appropriate error message when the sqlite_master table contains a CREATE TABLE AS statement. Formerly this caused either an assertion fault or null pointer dereference. Problem found by OSSFuzz on the GDAL project.
Incorrect assert() statement removed.
Fix a problem with using the LIKE optimization on an INTEGER PRIMARY KEY.

Revision 1.75 / (download) - annotate - [select for diffs], Wed Jan 24 13:44:14 2018 UTC (5 years, 10 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2018Q1-base, pkgsrc-2018Q1
Changes since 1.74: +5 -5 lines
Diff to previous 1.74 (colored)

sqlite3: updated to 3.22.0

Release 3.22.0:
The output of sqlite3_trace_v2() now shows each individual SQL statement run within a trigger.
Add the ability to read from WAL mode databases even if the application lacks write permission on the database and its containing directory, as long as the -shm and -wal files exist in that directory.
Added the rtreecheck() scalar SQL function to the R-Tree extension.
Added the sqlite3_vtab_nochange() and sqlite3_value_nochange() interfaces to help virtual table implementations optimize UPDATE operations.
Added the sqlite3_vtab_collation() interface.
Added support for the "^" initial token syntax in FTS5.
New extensions:
The Zipfile virtual table can read and write a ZIP Archive.
Added the fsdir(PATH) table-valued function to the fileio.c extension, for listing the files in a directory.
The sqlite_btreeinfo eponymous virtual table for introspecting and estimating the sizes of the btrees in a database.
The Append VFS is a VFS shim that allows an SQLite database to be appended to some other file. This allows (for example) a database to be appended to an executable that then opens and reads the database.
Query planner enhancements:
The optimization that uses an index to quickly compute an aggregate min() or max() is extended to work with indexes on expressions.
The decision of whether to implement a FROM-clause subquery as a co-routine or using query flattening now considers whether the result set of the outer query is "complex" (if it contains functions or expression subqueries). A complex result set biases the decision toward the use of co-routines.
The planner avoids query plans that use indexes with unknown collating functions.
The planner omits unused LEFT JOINs even if they are not the right-most joins of a query.
Other performance optimizations:
A smaller and faster implementation of text to floating-point conversion subroutine: sqlite3AtoF().
The Lemon parser generator creates a faster parser.
Use the strcspn() C-library routine to speed up the LIKE and GLOB operators.
Improvements to the command-line shell:
The ".schema" command shows the structure of virtual tables.
Added support for reading and writing SQL Archive files using the .archive command.
Added the experimental .expert command
Added the ".eqp trigger" variant of the ".eqp" command
Enhance the ".lint fkey-indexes" command so that it works with WITHOUT ROWID tables.
If the filename argument to the shell is a ZIP archive rather than an SQLite database, then the shell automatically opens that ZIP archive using the Zipfile virtual table.
Added the edit() SQL function.
Added the .excel command to simplify exporting database content to a spreadsheet.
Databases are opened using Append VFS when the --append flag is used on the command line or with the .open command.
Enhance the SQLITE_ENABLE_UPDATE_DELETE_LIMIT compile-time option so that it works for WITHOUT ROWID tables.
Provide the sqlite_offset(X) SQL function that returns the byte offset into the database file to the beginning of the record holding value X, when compiling with -DSQLITE_ENABLE_OFFSET_SQL_FUNC.
Bug fixes

Revision 1.74 / (download) - annotate - [select for diffs], Mon Oct 30 18:36:13 2017 UTC (6 years, 1 month ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q4-base, pkgsrc-2017Q4
Changes since 1.73: +5 -5 lines
Diff to previous 1.73 (colored)

sqlite3: updated to 3.21.0

Release 3.21.0:

Take advantage of the atomic-write capabilities in the F2FS filesystem when available, for greatly reduced transaction overhead. This currently requires the SQLITE_ENABLE_BATCH_ATOMIC_WRITE compile-time option.
Allow ATTACH and DETACH commands to work inside of a transaction.
Allow WITHOUT ROWID virtual tables to be writable if the PRIMARY KEY contains exactly one column.
The "fsync()" that occurs after the header is written in a WAL reset now uses the sync settings for checkpoints. This means it will use a "fullfsync" on macs if PRAGMA checkpoint_fullfsync set on.
The sqlite3_sourceid() function tries to detect if the source code has been modified from what is checked into version control and if there are modifications, the last four characters of the version hash are shown as "alt1" or "alt2". The objective is to detect accidental and/or careless edits. A forger can subvert this feature.
Improved de-quoting of column names for CREATE TABLE AS statements with an aggregate query on the right-hand side.
Fewer "stat()" system calls issued by the unix VFS.
Enhanced the LIKE optimization so that it works with an ESCAPE clause.
Enhanced PRAGMA integrity_check and PRAGMA quick_check to detect obscure row corruption that they were formerly missing. Also update both pragmas so that they return error text rather than SQLITE_CORRUPT when encountering corruption in records.
The query planner now prefers to implement FROM-clause subqueries using co-routines rather using the query flattener optimization. Support for the use of co-routines for subqueries may no longer be disabled.
Pass information about !=, IS, IS NOT, NOT NULL, and IS NULL constraints into the xBestIndex method of virtual tables.
Enhanced the CSV virtual table so that it accepts the last row of input if the final new-line character is missing.
Remove the rarely-used "scratch" memory allocator. Replace it with the SQLITE_CONFIG_SMALL_MALLOC configuration setting that gives SQLite a hint that large memory allocations should be avoided when possible.
Added the swarm virtual table to the existing union virtual table extension.
Added the sqlite_dbpage virtual table for providing direct access to pages of the database file. The source code is built into the amalgamation and is activated using the -DSQLITE_ENABLE_DBPAGE_VTAB compile-time option.
Add a new type of fts5vocab virtual table - "instance" - that provides direct access to an FTS5 full-text index at the lowest possible level.
Remove a call to rand_s() in the Windows VFS since it was causing problems in Firefox on some older laptops.
The src/shell.c source code to the command-line shell is no longer under version control. That file is now generated as part of the build process.
Miscellaneous microoptimizations reduce CPU usage by about 2.1%.
Bug fixes

Revision 1.73 / (download) - annotate - [select for diffs], Fri Aug 25 05:27:53 2017 UTC (6 years, 3 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q3-base, pkgsrc-2017Q3
Changes since 1.72: +5 -5 lines
Diff to previous 1.72 (colored)

Release 3.20.1:
Fix a potential memory leak in the new sqlite3_result_pointer() interface.

Revision 1.72 / (download) - annotate - [select for diffs], Mon Aug 14 15:25:09 2017 UTC (6 years, 3 months ago) by jlam
Branch: MAIN
Changes since 1.71: +5 -5 lines
Diff to previous 1.71 (colored)

databases/sqlite3-docs: Update checksum and PLIST to match version.

This package uses sqlite3/Makefile.version to set the package
version, but the checksum was for the distfile of the previous
version.  Update the checksum to the correct distfile and fix the
resulting PLIST.

Revision 1.71 / (download) - annotate - [select for diffs], Sat Jun 10 19:14:00 2017 UTC (6 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q2-base, pkgsrc-2017Q2
Changes since 1.70: +5 -5 lines
Diff to previous 1.70 (colored)

Release 3.19.3:
Fix a bug associated with auto_vacuum that can lead to database corruption. The bug was introduced in version 3.16.0.

Revision 1.70 / (download) - annotate - [select for diffs], Wed May 31 17:31:51 2017 UTC (6 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.69: +5 -5 lines
Diff to previous 1.69 (colored)

SQLite Release 3.19.2 On 2017-05-25

Fix more bugs in the LEFT JOIN flattening optimization. Ticket 7fde638e94287d2c.

Changes carried forward from version 3.19.1 (2017-05-24):

Fix a bug in the LEFT JOIN flattening optimization. Ticket cad1ab4cb7b0fc.
Remove a surplus semicolon that was causing problems for older versions of MSVC.

Revision 1.69 / (download) - annotate - [select for diffs], Wed May 24 19:41:03 2017 UTC (6 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.68: +5 -5 lines
Diff to previous 1.68 (colored)

SQLite Release 3.19.0
The SQLITE_READ authorizer callback is invoked once with a column name that is an empty string for every table referenced in a query from which no columns are extracted.
When using an index on an expression, try to use expression values already available in the index, rather than loading the original columns and recomputing the expression.
Enhance the flattening optimization so that it is able to flatten views on the right-hand side of a LEFT JOIN.
Use replace() instead of char() for escaping newline and carriage-return characters embedded in strings in the .dump output from the command-line shell.
Avoid unnecessary foreign key processing in UPDATE statements that do not touch the columns that are constrained by the foreign keys.
On a DISTINCT query that uses an index, try to skip ahead to the next distinct entry using the index rather than stepping through rows, when an appropriate index is available.
Avoid unnecessary invalidation of sqlite3_blob handles when making changes to unrelated tables.
Transfer any terms of the HAVING clause that use only columns mentioned in the GROUP BY clause over to the WHERE clause for faster processing.
Reuse the same materialization of a VIEW if that VIEW appears more than once in the same query.
Enhance PRAGMA integrity_check so that it identifies tables that have two or more rows with the same rowid.
Enhance the FTS5 query syntax so that column filters may be applied to arbitrary expressions.
Enhance the json_extract() function to cache and reuse parses of JSON input text.
Added the anycollseq.c loadable extension that allows a generic SQLite database connection to read a schema that contains unknown and/or application-specific collating sequences.

Bug Fixes:
Fix a problem in REPLACE that can result in a corrupt database containing two or more rows with the same rowid.
Fix a problem in PRAGMA integrity_check that was causing a subsequent VACUUM to behave suboptimally.
Fix the PRAGMA foreign_key_check command so that it works correctly with foreign keys on WITHOUT ROWID tables.
Disallow leading zeros in numeric constants in JSON.
Disallow control characters inside of strings in JSON.
Limit the depth of recursion for JSON objects and arrays in order to avoid excess stack usage in the recursive descent parser.

Revision 1.68 / (download) - annotate - [select for diffs], Thu Mar 30 15:55:12 2017 UTC (6 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.67: +5 -5 lines
Diff to previous 1.67 (colored)

Release 3.18.0:

Added the PRAGMA optimize command
The SQLite version identifier returned by the sqlite_source_id() SQL function and the sqlite3_sourceid() C API and found in the SQLITE_SOURCE_ID macro is now a 64-digit SHA3-256 hash instead of a 40-digit SHA1 hash.
Added the json_patch() SQL function to the JSON1 extension.
Enhance the LIKE optimization so that it works for arbitrary expressions on the left-hand side as long as the LIKE pattern on the right-hand side does not begin with a digit or minus sign.
Added the sqlite3_set_last_insert_rowid() interface and use the new interface in the FTS3, FTS4, and FTS5 extensions to ensure that the sqlite3_last_insert_rowid() interface always returns reasonable values.
Enhance PRAGMA integrity_check and PRAGMA quick_check so that they verify CHECK constraints.
Enhance the query plans for joins to detect empty tables early and halt without doing unnecessary work.
Enhance the sqlite3_mprintf() family of interfaces and the printf SQL function to put comma separators at the thousands marks for integers, if the "," format modifier is used in between the "%" and the "d" (example: "%,d").
Added the -DSQLITE_MAX_MEMORY=N compile-time option.
Added the .sha3sum dot-command and the .selftest dot-command to the command-line shell
Begin enforcing SQLITE_LIMIT_VDBE_OP. This can be used, for example, to prevent excessively large prepared statements in systems that accept SQL queries from untrusted users.
Various performance improvements.

Bug Fixes:
Ensure that indexed expressions with collating sequences are handled correctly. Fix for ticket eb703ba7b50c1a5.
Fix a bug in the 'start of ...' modifiers for the date and time functions. Ticket 6097cb92745327a1
Fix a potential segfault in complex recursive triggers, resulting from a bug in the OP_Once opcode introduced as part of a performance optimization in version 3.15.0. Ticket 06796225f59c057c
In the RBU extension, add extra sync operations to avoid the possibility of corruption following a power failure.
The sqlite3_trace_v2() output for nested SQL statements should always begin with a "--" comment marker.

Revision 1.67 / (download) - annotate - [select for diffs], Mon Feb 13 17:44:01 2017 UTC (6 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2017Q1-base, pkgsrc-2017Q1
Changes since 1.66: +5 -5 lines
Diff to previous 1.66 (colored)

SQLite Release 3.17.0 On 2017-02-13
* Approximately 25% better performance from the R-Tree extension.
* Uses compiler built-ins (ex: __builtin_bswap32() or _byteswap_ulong()) for byteswapping when available.
* Uses the sqlite3_blob key/value access object instead of SQL for pulling content out of R-Tree nodes
* Other miscellaneous enhancements such as loop unrolling.
* Add the SQLITE_DEFAULT_LOOKASIDE compile-time option.
* Increase the default lookaside size from 512,125 to 1200,100 as this provides better performance while only adding 56KB of extra memory per connection. Memory-sensitive applications can restore the old default at compile-time, start-time, or run-time.
* Use compiler built-ins __builtin_sub_overflow(), __builtin_add_overflow(), and __builtin_mul_overflow() when available. (All compiler built-ins can be omitted with the SQLITE_DISABLE_INTRINSIC compile-time option.)
* Added the SQLITE_ENABLE_NULL_TRIM compile-time option, which can result in significantly smaller database files for some applications, at the risk of being incompatible with older versions of SQLite.
* Change SQLITE_DEFAULT_PCACHE_INITSZ from 100 to 20, for improved performance.
* Added the SQLITE_UINT64_TYPE compile-time option as an analog to SQLITE_INT64_TYPE.
* Perform some UPDATE operations in a single pass instead of in two passes.
* Enhance the session extension to support WITHOUT ROWID tables.
* Fixed performance problems and potential stack overflows when creating views from multi-row VALUES clauses with hundreds of thousands of rows.
* Added the sha1.c extension.
* In the command-line shell, enhance the ".mode" command so that it restores the default column and row separators for modes "line", "list", "column", and "tcl".
* Enhance the SQLITE_DIRECT_OVERFLOW_READ option so that it works in WAL mode as long as the pages being read are not in the WAL file.
* Enhance the LEMON parser generator so that it can store the parser object as a stack variable rather than allocating space from the heap and make use of that enhancement in the amalgamation.
* Other performance improvements. Uses about 6.5% fewer CPU cycles.

Bug Fixes:
* Throw an error if the ON clause of a LEFT JOIN references tables to the right of the ON clause. This is the same behavior as PostgreSQL. Formerly, SQLite silently converted the LEFT JOIN into an INNER JOIN.
* Use the correct affinity for columns of automatic indexes.
* Ensure that the sqlite3_blob_reopen() interface can correctly handle short rows.

Revision 1.66 / (download) - annotate - [select for diffs], Sat Jan 7 10:23:00 2017 UTC (6 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.65: +5 -5 lines
Diff to previous 1.65 (colored)

Changes 3.16.2:
Fix the REPLACE statement for WITHOUT ROWID tables that lack secondary indexes so that it works correctly with triggers and foreign keys. This was a new bug caused by performance optimizations added in version 3.16.0. Ticket 30027b613b4
Fix the sqlite3_value_text() interface so that it correctly translates content generated by zeroblob() into a string of all 0x00 characters. This is a long-standing issue discovered after the 3.16.1 release by OSS-Fuzz
Fix the bytecode generator to deal with a subquery in the FROM clause that is itself a UNION ALL where one side of the UNION ALL is a view that contains an ORDER BY. This is a long-standing issue that was discovered after the release of 3.16.1. See ticket 190c2507.
Adjust the sqlite3_column_count() API so it more often returns the same values for PRAGMA statements as it did in prior releases, to minimize disruption to applications that might be using that interface in unexpected ways.

Revision 1.65 / (download) - annotate - [select for diffs], Thu Jan 5 17:49:54 2017 UTC (6 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.64: +5 -5 lines
Diff to previous 1.64 (colored)

Changes 3.16.1:
Fix a bug concerning the use of row values within triggers (see ticket 8c9458e7) that was in version 3.15.0 but was not reported until moments after the 3.16.0 release was published.

Revision 1.64 / (download) - annotate - [select for diffs], Mon Jan 2 17:52:24 2017 UTC (6 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.63: +5 -5 lines
Diff to previous 1.63 (colored)

SQLite Release 3.16.0 On 2017-01-02

Uses 9% fewer CPU cycles. (See the CPU performance measurement report for details on how the this performance increase was computed.)
Added experimental support for PRAGMA functions.
Added the SQLITE_DBCONFIG_NO_CKPT_ON_CLOSE option to sqlite3_db_config().
Enhance the date and time functions so that the 'unixepoch' modifier works for the full span of supported dates.
Changed the default configuration of the lookaside memory allocator from 500 slots of 128 bytes each into 125 slots of 512 bytes each.
Enhanced "WHERE x NOT NULL" partial indexes so that they are usable if the "x" column appears in a LIKE or GLOB operator.
Enhanced sqlite3_interrupt() so that it interrupts checkpoint operations that are in process.
Enhanced the LIKE and GLOB matching algorithm to be faster for cases when the pattern contains multiple wildcards.
Added the SQLITE_FCNTL_WIN32_GET_HANDLE file control opcode.
Added ".mode quote" to the command-line shell.
Added ".lint fkey-indexes" to the command-line shell.
Added the .imposter dot-command to the command-line shell.
Added the remember(V,PTR) SQL function as a loadable extension.
Rename the SQLITE_OMIT_BUILTIN_TEST compile-time option to SQLITE_UNTESTABLE to better reflect the implications of using it.

Bug Fixes:
Fix a long-standing bug in the query planner that caused incorrect results on a LEFT JOIN where the left-hand table is a subquery and the join constraint is a bare column name coming from the left-hand subquery. Ticket 2df0107b.
Correctly handle the integer literal -0x8000000000000000 in the query planner.

Revision 1.63 / (download) - annotate - [select for diffs], Tue Dec 20 14:20:27 2016 UTC (6 years, 11 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q4-base, pkgsrc-2016Q4
Changes since 1.62: +5 -5 lines
Diff to previous 1.62 (colored)

Add missing sqlite 3.15.2 commit

Revision 1.62 / (download) - annotate - [select for diffs], Fri Nov 4 20:31:34 2016 UTC (7 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.61: +5 -5 lines
Diff to previous 1.61 (colored)

Changes 3.15.1:
* Added SQLITE_FCNTL_WIN32_GET_HANDLE file control opcode.
Bug Fixes:
* Fix the VACUUM command so that it spills excess content to disk rather than holding everything in memory, and possible causing an out-of-memory error for larger database files. This fixes an issue introduced by version 3.15.0.
* Fix a case (present since 3.8.0 - 2013-08-26) where OR-connected terms in the ON clause of a LEFT JOIN might cause incorrect results.
* Fix a case where the use of row values in the ON clause of a LEFT JOIN might cause incorrect results.

Revision 1.61 / (download) - annotate - [select for diffs], Mon Oct 17 12:17:50 2016 UTC (7 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.60: +5 -5 lines
Diff to previous 1.60 (colored)

Changes 3.15.0:
Added support for row values.
Allow deterministic SQL functions in the WHERE clause of a partial index.
Added the "modeof=filename" URI parameter on the unix VFS
Added the ability to VACUUM an ATTACH-ed database.
Enhancements to the command-line shell:
Add the ".testcase" and ".check" dot-commands.
Added the --new option to the ".open" dot-command, causing any prior content in the database to be purged prior to opening.
Enhance the fts5vocab virtual table to handle "ORDER BY term" efficiently.
Miscellaneous micro-optimizations reduce CPU usage by more than 7% on common workloads. Most optimization in this release has been on the front-end (sqlite3_prepare_v2()).

Bug Fixes:

The multiply operator now correctly detects 64-bit integer overflow and promotes to floating point in all corner-cases.
Correct handling of columns with redundant unique indexes when those columns are used on the LHS of an IN operator.
Skip NULL entries on range queries in indexes on expressions.
Ensure that the AUTOINCREMENT counters in the sqlite_sequence table are initialized doing "Xfer Optimization" on "INSERT ... SELECT" statements.
Make sure the ORDER BY LIMIT optimization (from check-in 559733b09e) works with IN operators on INTEGER PRIMARY KEYs.

Revision 1.60 / (download) - annotate - [select for diffs], Tue Sep 13 10:48:24 2016 UTC (7 years, 2 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q3-base, pkgsrc-2016Q3
Changes since 1.59: +5 -5 lines
Diff to previous 1.59 (colored)

SQLite Release 3.14.2:
* Improved support for using the STDCALL calling convention in winsqlite3.dll.
* Fix the sqlite3_trace_v2() interface so that it is disabled if either the callback or the mask arguments are zero, in accordance with the documentation.
* Fix commenting errors and improve the comments generated on EXPLAIN listings when the -DSQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is used.
* Fix the ".read" command in the command-line shell so that it understands that its input is not interactive.
* Correct affinity computations for a SELECT on the RHS of an IN operator.
* The ORDER BY LIMIT optimization is not valid unless the inner-most IN operator loop is actually used by the query plan. Fix for ticket 0c4df46116e90f92.
* Fix an internal code generator problem that was causing some DELETE operations to no-op.

Revision 1.59 / (download) - annotate - [select for diffs], Sun Aug 14 11:19:09 2016 UTC (7 years, 3 months ago) by adam
Branch: MAIN
Changes since 1.58: +5 -5 lines
Diff to previous 1.58 (colored)

Changes 3.14.1:
* A performance enhancement to the page-cache "truncate" operation reduces COMMIT time by dozens of milliseconds on systems with a large page cache.
* Fix to the --rbu option of sqldiff.

Revision 1.58 / (download) - annotate - [select for diffs], Tue Aug 9 14:54:25 2016 UTC (7 years, 4 months ago) by adam
Branch: MAIN
Changes since 1.57: +5 -5 lines
Diff to previous 1.57 (colored)

Changes 3.14.0:
Added support for WITHOUT ROWID virtual tables.
Improved the query planner so that the OR optimization can be used on virtual tables even if one or more of the disjuncts use the LIKE, GLOB, REGEXP, MATCH operators.
Added the CSV virtual table for reading RFC 4180 formatted comma-separated value files.
Added the carray() table-valued function extension.
Enabled persistent loadable extensions using the new SQLITE_OK_LOAD_PERMANENTLY return code from the extension entry point.
Added the SQLITE_DBSTATUS_CACHE_USED_SHARED option to sqlite3_db_status().
Add the vfsstat.c loadable extension - a VFS shim that measures I/O together with an eponymous virtual table that provides access to the measurements.
Improved algorithm for running queries with both an ORDER BY and a LIMIT where only the inner-most loop naturally generates rows in the correct order.
Enhancements to Lemon parser generator, so that it generates a faster parser.
The PRAGMA compile_options command now attempts to show the version number of the compiler that generated the library.
Enhance PRAGMA table_info so that it provides information about eponymous virtual tables.
Added the "win32-none" VFS, analogous to the "unix-none" VFS, that works like the default "win32" VFS except that it ignores all file locks.
The query planner uses a full scan of a partial index instead of a full scan of the main table, in cases where that makes sense.
Allow table-valued functions to appear on the right-hand side of an IN operator.
Created the dbhash.exe command-line utility.
Added two new C-language interfaces: sqlite3_expanded_sql() and sqlite3_trace_v2(). These new interfaces subsume the functions of sqlite3_trace() and sqlite3_profile() which are now deprecated.
Added the json_quote() SQL function to the json1 extension.
Disable the authorizer callback while reparsing the schema.
Added the SQLITE_ENABLE_UNKNOWN_SQL_FUNCTION compile-time option and turned that option on by default when building the command-line shell.

Bug Fixes:
Fix the ALTER TABLE command so that it does not corrupt descending indexes when adding a column to a legacy file format database.
Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence.
Improved the cost estimation for an index scan which includes a WHERE clause that can be partially or fully evaluated using columns in the index and without having to do a table lookup. This fixes a performance regression that occurred for some obscure queries following the ORDER BY LIMIT optimization introduced in version 3.12.0.

Revision 1.57 / (download) - annotate - [select for diffs], Sat May 21 11:19:30 2016 UTC (7 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q2-base, pkgsrc-2016Q2
Changes since 1.56: +5 -5 lines
Diff to previous 1.56 (colored)

Release 3.13.0:

Postpone I/O associated with TEMP files for as long as possible, with the hope that the I/O can ultimately be avoided completely.
Merged the session extension into trunk.
Added the ".auth ON|OFF" command to the command-line shell.
Added the "--indent" option to the ".schema" and ".fullschema" commands of the command-line shell, to turn on pretty-printing.
Added the ".eqp full" option to the command-line shell, that does both EXPLAIN and EXPLAIN QUERY PLAN on each statement that is evaluated.
Improved unicode filename handling in the command-line shell on Windows.
Improved resistance against goofy query planner decisions caused by incomplete or incorrect modifications to the sqlite_stat1 table by the application.
Added the sqlite3_db_config(db,SQLITE_DBCONFIG_ENABLE_LOAD_EXTENSION) interface which allows the sqlite3_load_extension() C-API to be enabled while keeping the load_extension() SQL function disabled for security.
Change the temporary directory search algorithm on Unix to allow directories with write and execute permission, but without read permission, to serve as temporary directories. Apply this same standard to the "." fallback directory.

Bug Fixes:
Fix a problem with the multi-row one-pass DELETE optimization that was causing it to compute incorrect answers with a self-referential subquery in the WHERE clause. Fix for ticket dc6ebeda9396087
Fix a possible segfault with DELETE when table is a rowid table with an INTEGER PRIMARY KEY and the WHERE clause contains a OR and the table has one or more indexes that are able to trigger the OR optimization, but none of the indexes reference any table columns other than the INTEGER PRIMARY KEY. Ticket 16c9801ceba49.
When checking for the WHERE-clause push-down optimization, verify that all terms of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket f7f8c97e97597.
Fix a locking race condition in Windows that can occur when two or more processes attempt to recover the same hot journal at the same time.

Revision 1.56 / (download) - annotate - [select for diffs], Wed Apr 20 05:04:44 2016 UTC (7 years, 7 months ago) by adam
Branch: MAIN
Changes since 1.55: +5 -5 lines
Diff to previous 1.55 (colored)

Changes 3.12.2:
Fix a backwards compatibility problem in version 3.12.0 and 3.12.1: Columns declared as "INTEGER" PRIMARY KEY (with quotes around the datatype keyword) where not being recognized as an INTEGER PRIMARY KEY, which resulted in an incompatible database file.
Fix a bug (present since version 3.9.0) that can cause the DELETE operation to miss rows if PRAGMA reverse_unordered_selects is turned on.
Fix a bug in the code generator that can causes incorrect results if two or more virtual tables are joined and the virtual table used in outer loop of the join has an IN operator constraint.
Correctly interpret negative "PRAGMA cache_size" values when determining the cache size used for sorting large amounts of data.

Revision 1.55 / (download) - annotate - [select for diffs], Sat Apr 9 09:25:39 2016 UTC (7 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.54: +5 -5 lines
Diff to previous 1.54 (colored)

Release 3.12.1
Fix a boundary condition error introduced by version 3.12.0 that can result in a crash during heavy SAVEPOINT usage.
Fix views so that they inherit column datatypes from the table that they are defined against, when possible.
Fix the query planner so that IS and IS NULL operators are able to drive an index on a LEFT OUTER JOIN.

Revision 1.54 / (download) - annotate - [select for diffs], Fri Apr 8 07:54:27 2016 UTC (7 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.53: +5 -5 lines
Diff to previous 1.53 (colored)

Release 3.12.0

Potentially Disruptive Change:
The SQLITE_DEFAULT_PAGE_SIZE is increased from 1024 to 4096. The SQLITE_DEFAULT_CACHE_SIZE is changed from 2000 to -2000 so the same amount of cache memory is used by default. See the application note on the version 3.12.0 page size change for further information.

Performance enhancements:
Enhancements to the Lemon parser generator so that it creates a smaller and faster SQL parser.
Only create master journal files if two or more attached databases are all modified, do not have PRAGMA synchronous set to OFF, and do not have the journal_mode set to OFF, MEMORY, or WAL.
Only create statement journal files when their size exceeds a threshold. Otherwise the journal is held in memory and no I/O occurs. The threshold can be configured at compile-time using SQLITE_STMTJRNL_SPILL or at start-time using sqlite3_config(SQLITE_CONFIG_STMTJRNL_SPILL).
The query planner is able to optimize IN operators on virtual tables even if the xBestIndex method does not set the sqlite3_index_constraint_usage.omit flag of the virtual table column to the left of the IN operator.
The query planner now does a better job of optimizing virtual table accesses in a 3-way or higher join where constraints on the virtual table are split across two or more other tables of the join.
More efficient handling of application-defined SQL functions, especially in cases where the application defines hundreds or thousands of custom functions.
The query planner considers the LIMIT clause when estimating the cost of ORDER BY.
The configure script (on unix) automatically detects pread() and pwrite() and sets compile-time options to use those OS interfaces if they are available.
Reduce the amount of memory needed to hold the schema.
Other miscellaneous micro-optimizations for improved performance and reduced memory usage.

New Features:
Added the SQLITE_DBCONFIG_ENABLE_FTS3_TOKENIZER option to sqlite3_db_config() which allows the two-argument version of the fts3_tokenizer() SQL function to be enabled or disabled at run-time.
Added the sqlite3rbu_bp_progress() interface to the RBU extension.
The PRAGMA defer_foreign_keys=ON statement now also disables RESTRICT actions on foreign key.
Added the sqlite3_system_errno() interface.
Added the SQLITE_DEFAULT_SYNCHRONOUS and SQLITE_DEFAULT_WAL_SYNCHRONOUS compile-time options. The SQLITE_DEFAULT_SYNCHRONOUS compile-time option replaces the SQLITE_EXTRA_DURABLE option, which is no longer supported.
Enhanced the ".stats" command in the command-line shell to show more information about I/O performance obtained from /proc, when available.

Bug fixes:
Make sure the sqlite3_set_auxdata() values from multiple triggers within a single statement do not interfere with one another.
Fix the code generator for expressions of the form "x IN (SELECT...)" where the SELECT statement on the RHS is a correlated subquery.
Fix a harmless TSAN warning associated with the sqlite3_db_readonly() interface.

Revision 1.53 / (download) - annotate - [select for diffs], Sun Mar 6 09:57:51 2016 UTC (7 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2016Q1-base, pkgsrc-2016Q1
Changes since 1.52: +5 -5 lines
Diff to previous 1.52 (colored)

Changes 3.11.1:
Improvements to the Makefiles and build scripts used by VisualStudio.
Fix an FTS5 issue in which the 'optimize' command could cause index corruption.
Fix a buffer overread that might occur if FTS5 is used to query a corrupt database file.
Increase the maximum "scope" value for the spellfix1 extension from 6 to 30.

Revision 1.52 / (download) - annotate - [select for diffs], Tue Feb 16 13:46:04 2016 UTC (7 years, 9 months ago) by adam
Branch: MAIN
Changes since 1.51: +5 -5 lines
Diff to previous 1.51 (colored)

Changes 3.11.0:

General improvements:

Enhanced WAL mode so that it works efficiently with transactions that are larger than the cache_size.
Added the FTS5 detail option.
Added the "EXTRA" option to PRAGMA synchronous that does a sync of the containing directory when a rollback journal is unlinked in DELETE mode, for better durability. The SQLITE_EXTRA_DURABLE compile-time option enables PRAGMA synchronous=EXTRA by default.
Enhanced the query planner so that it is able to use a covering index as part of the OR optimization.
Avoid recomputing NOT NULL and CHECK constraints on unchanged columns in UPDATE statement.
Many micro-optimizations, resulting in a library that is faster than the previous release.
Enhancements to the command-line shell:

By default, the shell is now in "auto-explain" mode. The output of EXPLAIN commands is automatically formatted.
Added the ".vfslist" dot-command.
The SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is now turned on by default in the standard builds.

Enhancements to the TCL Interface:

If a database connection is opened with the "-uri 1" option, then URI filenames are honored by the "backup" and "restore" commands.
Added the "-sourceid" option to the "sqlite3" command.
Makefile improvements:

Improved pthreads detection in configure scripts.
Add the ability to do MSVC Windows builds from the amalgamation tarball.

Bug fixes

Fix an issue with incorrect sharing of VDBE temporary registers between co-routines that could cause incorrect query results in obscure cases. Ticket d06a25c84454a.
Fix a problem in the sqlite3_result_subtype() interface that could cause problems for the json1 extension under obscure circumstances. Fix for ticket f45ac567eaa9f9.
Escape control characters in JSON strings. Fix for ticket ad2559db380abf8.
Reenable the xCurrentTime and xGetLastError methods in the built-in unix VFSes as long as SQLITE_OMIT_DEPRECATED is not defined.

Backwards Compatibility:
Because of continuing security concerns, the two-argument version of of the seldom-used and little-known fts3_tokenizer() function is disabled unless SQLite is compiled with the SQLITE_ENABLE_FTS3_TOKENIZER.

Revision 1.51 / (download) - annotate - [select for diffs], Sun Jan 24 10:39:45 2016 UTC (7 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.50: +5 -5 lines
Diff to previous 1.50 (colored)

Changes 3.10.2:
* Version 3.10.0 introduced a case-folding bug in the LIKE operator which is fixed by this patch release.
* Fix a use-after-free that can occur when SQLite is compiled with -DSQLITE_HAS_CODEC.
* Fix the build so that it works with -DSQLITE_OMIT_WAL.
* Fix the configure script for the amalgamation so that the --readline option works again on Raspberry PIs.

Revision 1.50 / (download) - annotate - [select for diffs], Sat Jan 16 18:10:23 2016 UTC (7 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.49: +5 -5 lines
Diff to previous 1.49 (colored)

Changes 3.10.1:
* Add the SQLITE_FCNTL_JOURNAL_POINTER file control.
* Fix a 16-month-old bug in the query planner that could generate incorrect results when a scalar subquery attempts to use the block sorting optimization.

Revision 1.49 / (download) - annotate - [select for diffs], Fri Jan 8 14:43:10 2016 UTC (7 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.48: +5 -5 lines
Diff to previous 1.48 (colored)

Changes 3.10.0:

General improvements:
Added support for LIKE, GLOB, and REGEXP operators on virtual tables.
Added the colUsed field to sqlite3_index_info for use by the sqlite3_module.xBestIndex method.
Enhance the PRAGMA cache_spill statement to accept a 32-bit integer parameter which is the threshold below which cache spilling is prohibited.
On unix, if a symlink to a database file is opened, then the corresponding journal files are based on the actual filename, not the symlink name.
Added the "--transaction" option to sqldiff.
Added the sqlite3_db_cacheflush() interface.
Added the sqlite3_strlike() interface.
When using memory-mapped I/O map the database file read-only so that stray pointers and/or array overruns in the application cannot accidently modify the database file.
Added the experimental sqlite3_snapshot_get(), sqlite3_snapshot_open(), and sqlite3_snapshot_free() interfaces. These are subject to change or removal in a subsequent release.
Enhance the 'utc' modifier in the date and time functions so that it is a no-op if the date/time is known to already be in UTC. (This is not a compatibility break since the behavior has long been documented as "undefined" in that case.)
Added the json_group_array() and json_group_object() SQL functions in the json extension.
Added the SQLITE_LIKE_DOESNT_MATCH_BLOBS compile-time option.
Many small performance optimizations.

Portability enhancements:
Work around a sign-exension bug in the optimizer of the HP C compiler on HP/UX. (details)

Enhancements to the command-line shell:
Added the ".changes ON|OFF" and ".vfsinfo" dot-commands.
Translate between MBCS and UTF8 when running in cmd.exe on Windows.

Enhancements to makefiles:
Added the --enable-editline and --enable-static-shell options to the various autoconf-generated configure scripts.
Omit all use of "awk" in the makefiles, to make building easier for MSVC users.

Important fixes:
Fix inconsistent integer to floating-point comparison operations that could result in a corrupt index if the index is created on a table column that contains both large integers and floating point values of similar magnitude. Ticket 38a97a87a6.
Fix an infinite-loop in the query planner that could occur on malformed common table expressions.
Various bug fixes in the sqldiff tool.

Revision 1.48 / (download) - annotate - [select for diffs], Wed Nov 4 06:32:25 2015 UTC (8 years, 1 month ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2015Q4-base, pkgsrc-2015Q4
Changes since 1.47: +5 -6 lines
Diff to previous 1.47 (colored)

Changes 3.9.2:
* Fix the schema parser so that it interprets certain (obscure and ill-formed) CREATE TABLE statements the same as legacy.
* Fix a query planner problem that could result in an incorrect answer due to the use of automatic indexing in subqueries in the FROM clause of a correlated scalar subqueries.

Revision 1.47 / (download) - annotate - [select for diffs], Tue Nov 3 01:56:35 2015 UTC (8 years, 1 month ago) by agc
Branch: MAIN
Changes since 1.46: +2 -1 lines
Diff to previous 1.46 (colored)

Add SHA512 digests for distfiles for databases category

Problems found with existing distfiles:
No changes made to the cstore or mariadb55-client distinfo files.

Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden).  All existing
SHA1 digests retained for now as an audit trail.

Revision 1.46 / (download) - annotate - [select for diffs], Sat Oct 17 07:36:50 2015 UTC (8 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.45: +5 -5 lines
Diff to previous 1.45 (colored)

Changes 3.9.1:
Fix the json1 extension so that it does not recognize ASCII form-feed as a whitespace character, in order to comply with RFC-7159.
Add a few #ifdef and build script changes to address compilation issues that appeared after the 3.9.0 release.

Revision 1.45 / (download) - annotate - [select for diffs], Thu Oct 15 17:31:32 2015 UTC (8 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.44: +5 -4 lines
Diff to previous 1.44 (colored)

Changes 3.9.0:
Policy Changes:
* The version numbering conventions for SQLite are revised to use the emerging standard of semantic versioning.

New Features And Enhancements:
* Added the json1 extension module in the source tree, and in the amalgamation. Enable support using the SQLITE_ENABLE_JSON1 compile-time option.
* Added Full Text Search version 5 (FTS5) to the amalgamation, enabled using SQLITE_ENABLE_FTS5. FTS5 will be considered "experimental" (subject to incompatible changes) for at least one more release cycle.
* The CREATE VIEW statement now accepts an optional list of column names following the view name.
* Added support for indexes on expressions.
* Added support for table-valued functions in the FROM clause of a SELECT statement.
* Added support for eponymous virtual tables.
* A VIEW may now reference undefined tables and functions when initially created. Missing tables and functions are reported when the VIEW is used in a query.
* Added the sqlite3_value_subtype() and sqlite3_result_subtype() interfaced (used by the json1 extension).
* The query planner is now able to use partial indexes that contain AND-connected terms in the WHERE clause.
* 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.
* 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.

Other changes:
* The sqlite3_memory_alarm() interface, which has been deprecated and undocumented for 8 years, is changed into a no-op.

Important fixes:
* Fixed a critical bug in the SQLite Encryption Extension that could cause the database to become unreadable and unrecoverable if a VACUUM command changed the size of the encryption nonce.
* Added a memory barrier in the implementation of sqlite3_initialize() to help ensure that it is thread-safe.
* Fix the OR optimization so that it always ignores subplans that do not use an index.
* Do not apply the WHERE-clause pushdown optimization on terms that originate in the ON or USING clause of a LEFT JOIN.

Revision 1.44 / (download) - annotate - [select for diffs], Thu Jul 30 12:37:04 2015 UTC (8 years, 4 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2015Q3-base, pkgsrc-2015Q3
Changes since 1.43: +4 -4 lines
Diff to previous 1.43 (colored)

Restore an undocumented side-effect of PRAGMA cache_size: force the database schema to be parsed if the database has not been previously accessed.
Fix a long-standing problem in sqlite3_changes() for WITHOUT ROWID tables that was reported a few hours after the 3.8.11 release.

Revision 1.43 / (download) - annotate - [select for diffs], Tue Jul 28 07:18:22 2015 UTC (8 years, 4 months ago) by adam
Branch: MAIN
Changes since 1.42: +4 -4 lines
Diff to previous 1.42 (colored)

Changes 3.8.11:
Added the experimental RBU extension. Note that this extension is experimental and subject to change in incompatible ways.
Added the experimental FTS5 extension. Note that this extension is experimental and subject to change in incompatible ways.
Added the sqlite3_value_dup() and sqlite3_value_free() interfaces.
Enhance the spellfix1 extension to support ON CONFLICT clauses.
The IS operator is now able to drive indexes.
Enhance the query planner to permit automatic indexing on FROM-clause subqueries that are implemented by co-routine.
Disallow the use of "rowid" in common table expressions.
Added the PRAGMA cell_size_check command for better and earlier detection of database file corruption.
Added the matchinfo 'b' flag to the matchinfo() function in FTS3.
Improved fuzz-testing of database files, with fixes for problems found.
Add the fuzzcheck test program and automatically run this program using both SQL and database test cases on "make test".
Added the SQLITE_MUTEX_STATIC_VFS1 static mutex and use it in the Windows VFS.
The sqlite3_profile() callback is invoked (by sqlite3_reset() or sqlite3_finalize()) for statements that did not run to completion.
Enhance the page cache so that it can preallocate a block of memory to use for the initial set page cache lines. Set the default preallocation to 100 pages. Yields about a 5% performance increase on common workloads.
Miscellaneous micro-optimizations result in 22.3% more work for the same number of CPU cycles relative to the previous release. SQLite now runs twice as fast as version 3.8.0 and three times as fast as version 3.3.9. (Measured using cachegrind on the speedtest1.c workload on Ubuntu 14.04 x64 with gcc 4.8.2 and -Os. Your performance may vary.)
Added the sqlite3_result_zeroblob64() and sqlite3_bind_zeroblob64() interfaces.

Revision 1.42 / (download) - annotate - [select for diffs], Thu May 21 10:38:53 2015 UTC (8 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2015Q2-base, pkgsrc-2015Q2
Changes since 1.41: +4 -4 lines
Diff to previous 1.41 (colored)

Fix an index corruption issue introduced by version 3.8.7. An index with a TEXT key can be corrupted by an INSERT into the corresponding table if the table has two nested triggers that convert the key value to INTEGER and back to TEXT again.

Revision 1.41 / (download) - annotate - [select for diffs], Mon May 18 12:11:10 2015 UTC (8 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.40: +4 -4 lines
Diff to previous 1.40 (colored)

Make sqlite3_compileoption_used() responsive to the SQLITE_ENABLE_DBSTAT_VTAB compile-time option.
Fix a harmless warning in the command-line shell on some versions of MSVC.
Fix minor issues with the dbstat virtual table.

Revision 1.40 / (download) - annotate - [select for diffs], Sat May 9 09:32:56 2015 UTC (8 years, 7 months ago) by adam
Branch: MAIN
Changes since 1.39: +4 -4 lines
Diff to previous 1.39 (colored)

Changes 3.8.10:
Added the sqldiff.exe utility program for computing the differences between two SQLite database files.
Added the y format string to the matchinfo() function of FTS3.
Performance improvements for ORDER BY, VACUUM, CREATE INDEX, PRAGMA integrity_check, and PRAGMA quick_check.
Fix many obscure problems discovered while SQL fuzzing.
Identify all methods for important objects in the interface documentation. (example)
Made the American Fuzzy Lop fuzzer a standard part of SQLite's testing strategy.
Add the ".binary" and ".limits" commands to the command-line shell.
Make the "dbstat" virtual table part of standard builds when compiled with the SQLITE_ENABLE_DBSTAT_VTAB option.

Revision 1.39 / (download) - annotate - [select for diffs], Sat Apr 11 12:42:06 2015 UTC (8 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.38: +4 -4 lines
Diff to previous 1.38 (colored)

Changes 3.8.9:
Add VxWorks-7 as an officially supported and tested platform.
Added the sqlite3_status64() interface.
Fix memory size tracking so that it works even if SQLite uses more than 2GiB of memory.
Added the PRAGMA index_xinfo command.
Fix a potential 32-bit integer overflow problem in the sqlite3_blob_read() and sqlite3_blob_write() interfaces.
Ensure that prepared statements automatically reset on extended error codes of SQLITE_BUSY and SQLITE_LOCKED even when compiled using SQLITE_OMIT_AUTORESET.
Correct miscounts in the sqlite3_analyzer.exe utility related to WITHOUT ROWID tables.
Added the ".dbinfo" command to the command-line shell.
Improve the performance of fts3/4 queries that use the OR operator and at least one auxiliary fts function.
Fix a bug in the fts3 snippet() function causing it to omit leading separator characters from snippets that begin with the first token in a column.

Revision 1.38 / (download) - annotate - [select for diffs], Mon Mar 2 13:34:16 2015 UTC (8 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2015Q1-base, pkgsrc-2015Q1
Changes since 1.37: +4 -4 lines
Diff to previous 1.37 (colored)

Fix a bug (ticket 2326c258d02ead33) that can lead to incorrect results if the qualifying constraint of a partial index appears in the ON clause of a LEFT JOIN.
Added the ability to link against the "linenoise" command-line editing library in unix builds of the command-line shell.

Revision 1.37 / (download) - annotate - [select for diffs], Mon Feb 2 19:06:28 2015 UTC (8 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.36: +4 -4 lines
Diff to previous 1.36 (colored)

* Enhance sqlite3_wal_checkpoint_v2(TRUNCATE) interface so that it truncates the WAL file even if there is no checkpoint work to be done.

Revision 1.36 / (download) - annotate - [select for diffs], Tue Jan 20 20:11:07 2015 UTC (8 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.35: +4 -4 lines
Diff to previous 1.35 (colored)

* Fix a bug in the sorting logic, present since version 3.8.4, that can cause output to appear in the wrong order on queries that contains an ORDER BY clause, a LIMIT clause, and that have approximately 60 or more columns in the result set.

Revision 1.35 / (download) - annotate - [select for diffs], Fri Jan 16 21:01:19 2015 UTC (8 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.34: +4 -4 lines
Diff to previous 1.34 (colored)

Changes 3.8.8:

New Features:
* Added the PRAGMA data_version command that can be used to determine if a database file has been modified by another process.
* Added the SQLITE_CHECKPOINT_TRUNCATE option to the sqlite3_wal_checkpoint_v2() interface, with corresponding enhancements to PRAGMA wal_checkpoint.
* Added the sqlite3_stmt_scanstatus() interface, available only when compiled with SQLITE_ENABLE_STMT_SCANSTATUS.
* The sqlite3_table_column_metadata() is enhanced to work correctly on WITHOUT ROWID tables and to check for the existence of a a table if the column name parameter is NULL. The interface is now also included in the build by default, without requiring the SQLITE_ENABLE_COLUMN_METADATA compile-time option.
* Added the SQLITE_ENABLE_API_ARMOR compile-time option.
* Added the SQLITE_REVERSE_UNORDERED_SELECTS compile-time option.
* Added the SQLITE_SORTER_PMASZ compile-time option and SQLITE_CONFIG_PMASZ start-time option.
* Added the SQLITE_CONFIG_PCACHE_HDRSZ option to sqlite3_config() which makes it easier for applications to determine the appropriate amount of memory for use with SQLITE_CONFIG_PAGECACHE.
* The number of rows in a VALUES clause is no longer limited by SQLITE_LIMIT_COMPOUND_SELECT.
* Added the eval.c loadable extension that implements an eval() SQL function that will recursively evaluate SQL.

Performance Enhancements:
* Reduce the number of memcpy() operations involved in balancing a b-tree, for 3.2% overall performance boost.
* Improvements to cost estimates for the skip-scan optimization.
* The automatic indexing optimization is now capable of generating a partial index if that is appropriate.

Bug fixes:
* Ensure durability following a power loss with "PRAGMA journal_mode=TRUNCATE" by calling fsync() right after truncating the journal file.
* The query planner now recognizes that any column in the right-hand table of a LEFT JOIN can be NULL, even if that column has a NOT NULL constraint. Avoid trying to optimize out NULL tests in those cases.
* Make sure ORDER BY puts rows in ascending order even if the DISTINCT operator is implemented using a descending index.
* Fix data races that might occur under stress when running with many threads in shared cache mode where some of the threads are opening and closing connections.
* Fix obscure crash bugs found by american fuzzy lop.
* Work around a GCC optimizer bug (for gcc 4.2.1 on MacOS 10.7) that caused the R-Tree extension to compute incorrect results when compiled with -O3.

Other changes:
* Disable the use of the strchrnul() C-library routine unless it is specifically enabled using the -DHAVE_STRCHRNULL compile-time option.
* Improvements to the effectiveness and accuracy of the likelihood(), likely(), and unlikely() SQL hint functions.

Revision 1.34 / (download) - annotate - [select for diffs], Wed Dec 10 10:39:08 2014 UTC (9 years ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2014Q4-base, pkgsrc-2014Q4
Changes since 1.33: +4 -4 lines
Diff to previous 1.33 (colored)

Bug fix: Add in a mutex that was omitted from the previous release.

Revision 1.33 / (download) - annotate - [select for diffs], Mon Dec 8 11:04:32 2014 UTC (9 years ago) by adam
Branch: MAIN
Changes since 1.32: +4 -4 lines
Diff to previous 1.32 (colored)

* Bug fix: Ensure the cached KeyInfo objects (an internal abstraction not visible to the application) do not go stale when operating in shared cache mode and frequently closing and reopening some database connections while leaving other database connections on the same shared cache open continuously.
* Bug fix: Recognize that any column in the right-hand table of a LEFT JOIN can be NULL even if the column has a NOT NULL constraint. Do not apply optimizations that assume the column is never NULL.

Revision 1.32 / (download) - annotate - [select for diffs], Fri Oct 31 21:13:32 2014 UTC (9 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.31: +4 -4 lines
Diff to previous 1.31 (colored)

* In PRAGMA journal_mode=TRUNCATE mode, call fsync() immediately after truncating the journal file to ensure that the transaction is durable across a power loss.
* Fix an assertion fault that can occur when updating the NULL value of a field at the end of a table that was added using ALTER TABLE ADD COLUMN.
* Do not attempt to use the strchrnul() function from the standard C library unless the HAVE_STRCHRNULL compile-time option is set.
* Fix a couple of problems associated with running an UPDATE or DELETE on a VIEW with a rowid in the WHERE clause.

Revision 1.31 / (download) - annotate - [select for diffs], Sun Oct 19 20:37:47 2014 UTC (9 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.30: +4 -4 lines
Diff to previous 1.30 (colored)

Changes 3.8.7:

Performance Enhancements:
* Many micro-optimizations result in 20.3% more work for the same number of CPU cycles relative to the previous release. The cumulative performance increase since version 3.8.0 is 61%. (Measured using cachegrind on the speedtest1.c workload on Ubuntu 13.10 x64 with gcc 4.8.1 and -Os. Your performance may vary.)
* The sorter can use auxiliary helper threads to increase real-time response. This feature is off by default and may be enabled using the PRAGMA threads command or the SQLITE_DEFAULT_WORKER_THREADS compile-time option.
* Enhance the skip-scan optimization so that it is able to skip index terms that occur in the middle of the index, not just as the left-hand side of the index.
* Improved optimization of CAST operators.
* Various improvements in how the query planner uses sqlite_stat4 information to estimate plan costs.

New Features:
* Added new interfaces with 64-bit length parameters: sqlite3_malloc64(), sqlite3_realloc64(), sqlite3_bind_blob64(), sqlite3_result_blob64(), sqlite3_bind_text64(), and sqlite3_result_text64().
* Added the new interface sqlite3_msize() that returns the size of a memory allocation obtained from sqlite3_malloc64() and its variants.
* Added the SQLITE_LIMIT_WORKER_THREADS option to sqlite3_limit() and PRAGMA threads command for configuring the number of available worker threads.
* The spellfix1 extension allows the application to optionally specify the rowid for each INSERT.
* Added the User Authentication extension.

Bug Fixes:
* Fix a bug in the partial index implementation that might result in an incorrect answer if a partial index is used in a subquery or in a view.
* Fix a query planner bug that might cause a table to be scanned in the wrong direction (thus reversing the order of output) when a DESC index is used to implement the ORDER BY clause on a query that has an identical GROUP BY clause.
* Fix a bug in sqlite3_trace() that was causing it to sometimes fail to print an SQL statement if that statement needed to be re-prepared.
* Fix a faulty assert() statement.

Revision 1.30 / (download) - annotate - [select for diffs], Sun Aug 17 08:16:06 2014 UTC (9 years, 3 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2014Q3-base, pkgsrc-2014Q3
Changes since 1.29: +4 -4 lines
Diff to previous 1.29 (colored)

Changes 3.8.6:
Added support for hexadecimal integer literals in the SQL parser. (Ex: 0x123abc)
Enhanced the PRAGMA integrity_check command to detect UNIQUE and NOT NULL constraint violations.
Increase the maximum value of SQLITE_MAX_ATTACHED from 62 to 125.
Increase the timeout in WAL mode before issuing an SQLITE_PROTOCOL error from 1 second to 10 seconds.
Added the likely(X) SQL function.
The unicode61 tokenizer is now included in FTS4 by default.
Trigger automatic reprepares on all prepared statements when ANALYZE is run.
Added a new loadable extension source code file to the source tree: fileio.c
Add extension functions readfile(X) and writefile(X,Y) (using code copy/pasted from fileio.c in the previous bullet) to the command-line shell.
Added the .fullschema dot-command to the command-line shell.

Performance Enhancements:
Deactivate the DISTINCT keyword on subqueries on the right-hand side of the IN operator.
Add the capability of evaluating an IN operator as a sequence of comparisons as an alternative to using a table lookup. Use the sequence of comparisons implementation in circumstances where it is likely to be faster, such as when the right-hand side of the IN operator is small and/or changes frequently.
The query planner now uses sqlite_stat4 information (created by ANALYZE) to help determine if the skip-scan optimization is appropriate.
Ensure that the query planner never tries to use a self-made transient index in place of a schema-defined index.
Other minor tweaks to improve the quality of VDBE code.

Bug Fixes:
Fix a bug in CREATE UNIQUE INDEX, introduced when WITHOUT ROWID support added in version 3.8.2, that allows a non-unique NOT NULL column to be given a UNIQUE index.
Fix a bug in R-Tree extension, introduced in the previous release, that can cause an incorrect results for queries that use the rowid of the R-Tree on the left-hand side of an IN operator.
Fix the sqlite3_stmt_busy() interface so that it gives the correct answer for ROLLBACK statements that have been stepped but never reset.
Fix a bug in that would cause a null pointer to be dereferenced if a column with a DEFAULT that is an aggregate function tried to usee its DEFAULT.
CSV output from the command-line shell now always uses CRNL for the row separator and avoids inserting CR in front of NLs contained in data.
Fix a column affinity problem with the IN operator.
Fix the ANALYZE command so that it adds correct samples for WITHOUT ROWID tables in the sqlite_stat4 table.

Revision 1.29 / (download) - annotate - [select for diffs], Thu Jun 5 15:10:20 2014 UTC (9 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2014Q2-base, pkgsrc-2014Q2
Changes since 1.28: +4 -4 lines
Diff to previous 1.28 (colored)

Changes 3.8.5:
Added support for partial sorting by index.
Enhance the query planner so that it always prefers an index that uses a superset of WHERE clause terms relative to some other index.
Improvements to the automerge command of FTS4 to better control the index size for a full-text index that is subject to a large number of updates.
Added the sqlite3_rtree_query_callback() interface to R-Tree extension
Added new URI query parameters "nolock" and "immutable".
Use less memory by not remembering CHECK constraints on read-only database connections.
Enable the OR optimization for WITHOUT ROWID tables.
Render expressions of the form "x IN (?)" (with a single value in the list on the right-hand side of the IN operator) as if they where "x==?", Similarly optimize "x NOT IN (?)"
Add the ".system" and ".once" commands to the command-line shell.
Added the SQLITE_IOCAP_IMMUTABLE bit to the set of bits that can be returned by the xDeviceCharacteristics method of a VFS.
Added the SQLITE_TESTCTRL_BYTEORDER test control.

Bug Fixes:
OFFSET clause ignored on queries without a FROM clause.
Assertion fault on queries involving expressions of the form "x IN (?)".
Incorrect column datatype reported.
Duplicate row returned on a query against a table with more than 16 indices, each on a separate column, and all used via OR-connected constraints.
Partial index causes assertion fault on UPDATE OR REPLACE.
Crash when calling undocumented SQL function sqlite_rename_parent() with NULL parameters.
ORDER BY ignored if the query has an identical GROUP BY.
The group_concat(x,'') SQL function returns NULL instead of an empty string when all inputs are empty strings.
Fix a bug in the VDBE code generator that caused crashes when doing an INSERT INTO ... SELECT statement where the number of columns being inserted is larger than the number of columns in the destination table.
Fix a problem in CSV import in the command-line shell where if the leftmost field of the first row in the CSV file was both zero bytes in size and unquoted no data would be imported.
Fix a problem in FTS4 where the left-most column that contained the notindexed column name as a prefix was not indexed rather than the column whose name matched exactly.
Fix the sqlite3_db_readonly() interface so that it returns true if the database is read-only due to the file format write version number being too large.

Revision 1.28 / (download) - annotate - [select for diffs], Thu Apr 3 19:44:42 2014 UTC (9 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.27: +4 -4 lines
Diff to previous 1.27 (colored)

Add a one-character fix for a problem that might cause incorrect query results on a query that mixes DISTINCT, GROUP BY in a subquery, and ORDER BY.

Revision 1.27 / (download) - annotate - [select for diffs], Mon Mar 31 08:01:07 2014 UTC (9 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.26: +4 -4 lines
Diff to previous 1.26 (colored)

Fix a potential buffer overread that could result when trying to search a corrupt database file.

Revision 1.26 / (download) - annotate - [select for diffs], Thu Mar 13 13:36:19 2014 UTC (9 years, 9 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2014Q1-base, pkgsrc-2014Q1
Changes since 1.25: +4 -4 lines
Diff to previous 1.25 (colored)

Work around a C-preprocessor macro conflict that breaks the build for some configurations with Microsoft Visual Studio.
When computing the cost of the skip-scan optimization, take into account the fact that multiple seeks are required.

Revision 1.25 / (download) - annotate - [select for diffs], Mon Mar 10 17:03:29 2014 UTC (9 years, 9 months ago) by adam
Branch: MAIN
Changes since 1.24: +4 -4 lines
Diff to previous 1.24 (colored)

Changes 3.8.4:
Code optimization and refactoring for improved performance.
Add the ".clone" and ".save" commands to the command-line shell.
Update the banner on the command-line shell to alert novice users when they are using an ephemeral in-memory database.
Fix editline support in the command-line shell.
Add support for coverage testing of VDBE programs using the SQLITE_TESTCTRL_VDBE_COVERAGE verb of sqlite3_test_control().
Update the _FILE_OFFSET_BITS macro so that builds work again on QNX.
Change the datatype of SrcList.nSrc from type u8 to type int to work around an issue in the C compiler on AIX.
Get extension loading working on Cygwin.
Bug fix: Fix the char() SQL function so that it returns an empty string rather than an "out of memory" error when called with zero arguments.
Bug fix: DISTINCT now recognizes that a zeroblob and a blob of all 0x00 bytes are the same thing. Ticket [fccbde530a]
Bug fix: Compute the correct answer for queries that contain an IS NOT NULL term in the WHERE clause and also contain an OR term in the WHERE clause and are compiled with SQLITE_ENABLE_STAT4. Ticket [4c86b126f2]
Bug fix: Make sure "rowid" columns are correctly resolved in joins between normal tables and WITHOUT ROWID tables. Ticket [c34d0557f7]
Bug fix: Make sure the same temporary registers are not used in concurrent co-routines used to implement compound SELECT statements containing ORDER BY clauses, as such use can lead to incorrect answers. Ticket [8c63ff0eca]
Bug fix: Ensure that "ORDER BY random()" clauses do not get optimized out. Ticket [65bdeb9739]
Bug fix: Repair a name-resolution error that can occur in sub-select statements contained within a TRIGGER. Ticket [4ef7e3cfca]
Bug fix: Fix column default values expressions of the form "DEFAULT(-(-9223372036854775808))" so that they work correctly, initializing the column to a floating point value approximately equal to +9223372036854775808.0.

Revision 1.24 / (download) - annotate - [select for diffs], Thu Feb 13 07:30:31 2014 UTC (9 years, 9 months ago) by adam
Branch: MAIN
Changes since 1.23: +4 -4 lines
Diff to previous 1.23 (colored)

Fix a bug (ticket 4c86b126f2) that causes rows to go missing on some queries with OR clauses and IS NOT NULL operators in the WHERE clause, when the SQLITE_ENABLE_STAT3 or SQLITE_ENABLE_STAT4 compile-time options are used.
Fix a harmless compiler warning that was causing problems for VS2013.

Revision 1.23 / (download) - annotate - [select for diffs], Tue Feb 4 13:28:07 2014 UTC (9 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.22: +4 -4 lines
Diff to previous 1.22 (colored)

Changes 3.8.3:
Added support for common table expressions and the WITH clause.
Added the printf() SQL function.
Added SQLITE_DETERMINISTIC as an optional bit in the 4th argument to the sqlite3_create_function() and related interfaces, providing applications with the ability to create new functions that can be factored out of inner loops when they have constant arguments.
Add SQLITE_READONLY_DBMOVED error code, returned at the beginning of a transaction, to indicate that the underlying database file has been renamed or moved out from under SQLite.
Allow arbitrary expressions, including function calls and subqueries, in the filename argument to ATTACH.
Allow a VALUES clause to be used anywhere a SELECT statement is valid.
Reseed the PRNG used by sqlite3_randomness(N,P) when invoked with N==0. Automatically reseed after a fork() on unix.
Enhance the spellfix1 virtual table so that it can search efficiently by rowid.
Performance enhancements.
Improvements to the comments in the VDBE byte-code display when running EXPLAIN.
Add the "%token_class" directive to LEMON parser generator and use it to simplify the grammar.
Change the LEMON source code to avoid calling C-library functions that OpenBSD considers dangerous. (Ex: sprintf).
Bug fix: In the command-line shell CSV import feature, do not end a field when an escaped double-quote occurs at the end of a CRLN line.

Revision 1.22 / (download) - annotate - [select for diffs], Fri Dec 6 19:26:58 2013 UTC (10 years ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2013Q4-base, pkgsrc-2013Q4
Changes since 1.21: +4 -4 lines
Diff to previous 1.21 (colored)

Changes 3.8.2:
Changed the defined behavior for the CAST expression when floating point values greater than +9223372036854775807 are cast into into integers so that the result is the largest possible integer, +9223372036854775807, instead of the smallest possible integer, -9223372036854775808. After this change, CAST(9223372036854775809.0 as INT) yields +9223372036854775807 instead of -9223372036854775808. Potentially Incompatible Change!
Added support for WITHOUT ROWID tables.
Added the skip-scan optimization to the query planner.
Extended the virtual table interface, and in particular the sqlite3_index_info object to allow a virtual table to report its estimate on the number of rows that will be returned by a query.
Update the R-Tree extension to make use of the enhanced virtual table interface.
Add the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option.
Enhanced the comments that are inserted into EXPLAIN output when the SQLITE_ENABLE_EXPLAIN_COMMENTS compile-time option is enabled.
Performance enhancements in the VDBE, especially to the OP_Column opcode.
Factor constant subexpressions in inner loops out to the initialization code in prepared statements.
Enhanced the ".explain" output formatting of the command-line shell so that loops are indented to better show the structure of the program.
Enhanced the ".timer" feature of the command-line shell so that it shows wall-clock time in addition to system and user times.

Revision 1.21 / (download) - annotate - [select for diffs], Sat Oct 19 08:48:08 2013 UTC (10 years, 1 month ago) by adam
Branch: MAIN
Changes since 1.20: +4 -4 lines
Diff to previous 1.20 (colored)

Changes 3.8.1:
Added the unlikely() and likelihood() SQL functions to be used as hints to the query planner.
Enhancements to the query planner:
Take into account the fact WHERE clause terms that cannot be used with indices still probably reduce the number of output rows.
Estimate the sizes of table and index rows and use the smallest applicable B-Tree for full scans and "count(*)" operations.
Added the soft_heap_limit pragma.
Added support for SQLITE_ENABLE_STAT4
Added support for "sz=NNN" parameters at the end of sqlite_stat1.stat fields used to specify the average length in bytes for table and index rows.
Avoid running foreign-key constraint checks on an UPDATE if none of the modified columns are associated with foreign keys.
Added the SQLITE_MINIMUM_FILE_DESCRIPTOR compile-time option
Added the win32-longpath VFS on windows, permitting filenames up to 32K characters in length.
The Date And Time Functions are enhanced so that the current time (ex: julianday('now')) is always the same for multiple function invocations within the same sqlite3_step() call.
Add the "totype.c" extension, implementing the tointeger() and toreal() SQL functions.
FTS4 queries are better able to make use of docid<$limit constraints to limit the amount of I/O required.
Added the hidden fts4aux languageid column to the fts4aux virtual table.
The VACUUM command packs the database about 1% tighter.
The sqlite3_analyzer utility program is updated to provide better descriptions and to compute a more accurate estimate for "Non-sequential pages"
Refactor the implementation of PRAGMA statements to improve parsing performance.
The directory used to hold temporary files on unix can now be set using the SQLITE_TMPDIR environment variable, which takes precedence over the TMPDIR environment variable. The sqlite3_temp_directory global variable still has higher precedence than both environment variables, however.
Added the PRAGMA stats statement.
Bug fix: Return the correct answer for "SELECT count(*) FROM table" even if there is a partial index on the table.

Revision 1.20 / (download) - annotate - [select for diffs], Sun Sep 8 06:28:58 2013 UTC (10 years, 3 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2013Q3-base, pkgsrc-2013Q3
Changes since 1.19: +4 -4 lines
Diff to previous 1.19 (colored)

Fix an off-by-one error that caused quoted empty string at the end of a CRNL-terminated line of CSV input to be misread by the command-line shell.
Fix a query planner bug involving a LEFT JOIN with a BETWEEN or LIKE/GLOB constraint and then another INNER JOIN to the right that involves an OR constraint.
Fix a query planner bug that could result in a segfault when querying tables with a UNIQUE or PRIMARY KEY constraint with more than four columns.

Revision 1.19 / (download) - annotate - [select for diffs], Sat Aug 31 11:07:33 2013 UTC (10 years, 3 months ago) by adam
Branch: MAIN
Changes since 1.18: +4 -4 lines
Diff to previous 1.18 (colored)


Add support for partial indexes
Cut-over to the next generation query planner for faster and better query plans.
The EXPLAIN QUERY PLAN output no longer shows an estimate of the number of rows generated by each loop in a join.
Added the FTS4 notindexed option, allowing non-indexed columns in an FTS4 table.
Added the SQLITE_STMTSTATUS_VM_STEP option to sqlite3_stmt_status().
Added the cache_spill pragma.
Added the query_only pragma.
Added the defer_foreign_keys pragma and the sqlite3_db_status(db, SQLITE_DBSTATUS_DEFERRED_FKS,...) C-language interface.
Added the "percentile()" function as a loadable extension in the ext/misc subdirectory of the source tree.
Added the SQLITE_ALLOW_URI_AUTHORITY compile-time option.
Add the sqlite3_cancel_auto_extension(X) interface.
A running SELECT statement that lacks a FROM clause (or any other statement that never reads or writes from any database file) will not prevent a read transaction from closing.
Add the SQLITE_DEFAULT_AUTOMATIC_INDEX compile-time option. Setting this option to 0 disables automatic indices by default.
Issue an SQLITE_WARNING_AUTOINDEX warning on the SQLITE_CONFIG_LOG whenever the query planner uses an automatic index.
Added the SQLITE_FTS3_MAX_EXPR_DEPTH compile-time option.
Added an optional 5th parameter defining the collating sequence to the next_char() extension SQL function.
The SQLITE_BUSY_SNAPSHOT extended error code is returned in WAL mode when a read transaction cannot be upgraded to a write transaction because the read is on an older snapshot.
Enhancements to the sqlite3_analyzer utility program to provide size information separately for each individual index of a table, in addition to the aggregate size.
Allow read transactions to be freely opened and closed by SQL statements run from within the implementation of application-defined SQL functions if the function is called by a SELECT statement that does not access any database table.
Disable the use of posix_fallocate() on all (unix) systems unless the HAVE_POSIX_FALLOCATE compile-time option is used.
Update the ".import" command in the command-line shell to support multi-line fields and correct RFC-4180 quoting and to issue warning and/or error messages if the input text is not strictly RFC-4180 compliant.
Bug fix: In the unicode61 tokenizer of FTS4, treat all private code points as identifier symbols.
Bug fix: Bare identifiers in ORDER BY clauses bind more tightly to output column names, but identifiers in expressions bind more tightly to input column names. Identifiers in GROUP BY clauses always prefer output column names, however.
Bug fixes: Multiple problems in the legacy query optimizer were fixed by the move to NGQP.

Revision 1.18 / (download) - annotate - [select for diffs], Mon May 20 19:17:15 2013 UTC (10 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2013Q2-base, pkgsrc-2013Q2
Changes since 1.17: +4 -4 lines
Diff to previous 1.17 (colored)

Changes 3.7.17:
Add support for memory-mapped I/O.
Add the sqlite3_strglob() convenience interface.
Assigned the integer at offset 68 in the database header as the Application ID for when SQLite is used as an application file-format. Added the PRAGMA application_id command to query and set the Application ID.
Report rollback recovery in the error log as SQLITE_NOTICE_RECOVER_ROLLBACK. Change the error log code for WAL recover from SQLITE_OK to SQLITE_NOTICE_RECOVER_WAL.
Report the risky uses of unlinked database files and database filename aliasing as SQLITE_WARNING messages in the error log.
Added the SQLITE_TRACE_SIZE_LIMIT compile-time option.
Increase the default value of SQLITE_MAX_SCHEMA_RETRY to 50 and make sure that it is honored in every place that a schema change might force a statement retry.
Add a new test harness called "mptester" used to verify correct operation when multiple processes are using the same database file at the same time.
Enhance the extension loading mechanism to be more flexible (while still maintaining backwards compatibility) in two ways:
If the default entry point "sqlite3_extension_init" is not present in the loadable extension, also try an entry point "sqlite3_X_init" where "X" is based on the shared library filename. This allows every extension to have a different entry point, which allows them to be statically linked with no code changes.
The shared library filename passed to sqlite3_load_extension() may omit the filename suffix, and an appropriate architecture-dependent suffix (".so", ".dylib", or ".dll") will be added automatically.
Added many new loadable extensions to the source tree, including amatch, closure, fuzzer, ieee754, nextchar, regexp, spellfix, and wholenumber. See header comments on each extension source file for further information about what that extension does.
Enhance FTS3 to avoid using excess stack space when there are a huge number of terms on the right-hand side of the MATCH operator. A side-effect of this change is that the MATCH operator can only accommodate 12 NEAR operators at a time.
Enhance the fts4aux virtual table so that it can be a TEMP table.
Added the fts3tokenize virtual table to the full-text search logic.
Query planner enhancement: Use the transitive property of constraints to move constraints into the outer loops of a join whenever possible, thereby reducing the amount of work that needs to occur in inner loops.
Discontinue the use of posix_fallocate() on unix, as it does not work on all filesystems.
Improved tracing and debugging facilities in the Windows VFS.
Bug fix: Fix a potential database corruption bug in shared cache mode when one database connection is closed while another is in the middle of a write transaction.
Bug fix: Only consider AS names from the result set as candidates for resolving identifiers in the WHERE clause if there are no other matches. In the ORDER BY clause, AS names take priority over any column names.
Bug fix: Do not allow a virtual table to cancel the ORDER BY clause unless all outer loops are guaranteed to return no more than one row result.
Bug fix: Do not suppress the ORDER BY clause on a virtual table query if an IN constraint is used.
Bug fix: The command-line shell gives an exit code of 0 when terminated using the ".quit" command.
Bug fix: Make sure PRAGMA statements appear in sqlite3_trace() output.
Bug fix: When a compound query that uses an ORDER BY clause with a COLLATE operator, make sure that the sorting occurs according to the specified collation and that the comparisons associate with the compound query use the native collation.
Bug fix: Makes sure the authorizer callback gets a valid pointer to the string "ROWID" for the column-name parameter when doing an UPDATE that changes the rowid.
Bug fix: Do not move WHERE clause terms inside OR expressions that are contained within an ON clause of a LEFT JOIN.
Bug fix: Make sure an error is always reported when attempting to preform an operation that requires a collating sequence that is missing.

Revision 1.17 / (download) - annotate - [select for diffs], Mon Apr 15 15:33:46 2013 UTC (10 years, 7 months ago) by adam
Branch: MAIN
Changes since 1.16: +4 -4 lines
Diff to previous 1.16 (colored)

Fix a bug (present since version 3.7.13) that could result in database corruption on windows if two or more processes try to access the same database file at the same time and immediately after third process crashed in the middle of committing to that same file.

Revision 1.16 / (download) - annotate - [select for diffs], Mon Apr 1 18:56:41 2013 UTC (10 years, 8 months ago) by adam
Branch: MAIN
Changes since 1.15: +4 -4 lines
Diff to previous 1.15 (colored)

* Fix for a bug in the ORDER BY optimizer that was introduced in version 3.7.15 which would sometimes optimize out the sorting step when in fact the sort was required. Ticket a179fe7465
* Fix a long-standing bug in the CAST expression that would recognize UTF16 characters as digits even if their most-significant-byte was not zero. Ticket 689137afb6da41.
* Fix a bug in the NEAR operator of FTS3 when applied to subfields. Ticket 38b1ae018f.
* Fix a long-standing bug in the storage engine that would (very rarely) cause a spurious report of an SQLITE_CORRUPT error but which was otherwise harmless. Ticket 6bfb98dfc0c.
* The SQLITE_OMIT_MERGE_SORT option has been removed. The merge sorter is now a required component of SQLite.
* Fixed lots of spelling errors in the source-code comments

Revision 1.15 / (download) - annotate - [select for diffs], Thu Jan 10 17:12:30 2013 UTC (10 years, 11 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2013Q1-base, pkgsrc-2013Q1
Changes since 1.14: +4 -4 lines
Diff to previous 1.14 (colored)

Fix a bug, introduced in version 3.7.15, that causes an ORDER BY clause to be optimized out of a three-way join when the ORDER BY is actually required.

Revision 1.14 / (download) - annotate - [select for diffs], Thu Jan 3 20:46:18 2013 UTC (10 years, 11 months ago) by adam
Branch: MAIN
Changes since 1.13: +4 -4 lines
Diff to previous 1.13 (colored)

Fix a bug, introduced in version 3.7.15, that causes a segfault if the AS name of a result column of a SELECT statement is used as a logical term in the WHERE clause.

Revision 1.13 / (download) - annotate - [select for diffs], Sat Dec 15 18:42:33 2012 UTC (10 years, 11 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2012Q4-base, pkgsrc-2012Q4
Changes since 1.12: +4 -4 lines
Diff to previous 1.12 (colored)

Changes 3.7.15:
* Added the sqlite3_errstr() interface.
* Avoid invoking the sqlite3_trace() callback multiple times when a statement is automatically reprepared due to SQLITE_SCHEMA errors.
* Added support for Windows Phone 8 platforms
* Enhance IN operator processing to make use of indices with numeric affinities.
* Do full-table scans using covering indices when possible, under the theory that an index will be smaller and hence can be scanned with less I/O.
* Enhance the query optimizer so that ORDER BY clauses are more aggressively optimized, especially in joins where various terms of the ORDER BY clause come from separate tables of the join.
* Add the ability to implement FROM clause subqueries as coroutines rather that manifesting the subquery into a temporary table.
* Enhancements the command-line shell:
* Added the ".print" command
* Negative numbers in the ".width" command cause right-alignment
* Add the ".wheretrace" command when compiled with SQLITE_DEBUG
* Added the busy_timeout pragma.
* Added the instr() SQL function.
* Added the SQLITE_FCNTL_BUSYHANDLER file control, used to allow VFS implementations to get access to the busy handler callback.
* The xDelete method in the built-in VFSes now return SQLITE_IOERR_DELETE_NOENT if the file to be deleted does not exist.
* Enhanced support for QNX.
* Work around an optimizer bug in the MSVC compiler when targeting ARM.
* Bug fix: Avoid various concurrency problems in shared cache mode.
* Bug fix: Avoid a deadlock or crash if the backup API, shared cache, and the SQLite Encryption Extension are all used at once.
* Bug fix: SQL functions created using the TCL interface honor the "nullvalue" setting.
* Bug fix: Fix a 32-bit overflow problem on CREATE INDEX for databases larger than 16GB.
* Bug fix: Avoid segfault when using the COLLATE operator inside of a CHECK constraint or view in shared cache mode.

Revision 1.12 / (download) - annotate - [select for diffs], Thu Sep 6 20:29:41 2012 UTC (11 years, 3 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2012Q3-base, pkgsrc-2012Q3
Changes since 1.11: +4 -4 lines
Diff to previous 1.11 (colored)

Changes 3.7.14:
* Drop built-in support for OS/2. If you need to upgrade an OS/2 application to
  use this or a later version of SQLite, then add an application-defined VFS
  using the sqlite3_vfs_register() interface. The code removed in this release
  can serve as a baseline for the application-defined VFS.
* Ensure that floating point values are preserved exactly when reconstructing a
  database from the output of the ".dump" command of the command-line shell.
* Added the sqlite3_close_v2() interface.
* Updated the command-line shell so that it can be built using
* Improvements to the windows makefiles and build processes.
* Enhancements to PRAGMA integrity_check and PRAGMA quick_check so that they
  can optionally check just a single attached database instead of all attached
* Enhancements to WAL mode processing that ensure that at least one valid
  read-mark is available at all times, so that read-only processes can always
  read the database.
* Performance enhancements in the sorter used by ORDER BY and CREATE INDEX.
* Added the SQLITE_DISABLE_FTS4_DEFERRED compile-time option.
* Better handling of aggregate queries where the aggregate functions are
  contained within subqueries.
* Enhance the query planner so that it will try to use a covering index on
  queries that make use of or optimization.

Revision 1.11 / (download) - annotate - [select for diffs], Mon Jun 11 16:21:30 2012 UTC (11 years, 6 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2012Q2-base, pkgsrc-2012Q2
Changes since 1.10: +4 -4 lines
Diff to previous 1.10 (colored)

Changes 3.7.13:
* In-memory databases that are specified using URI filenames are allowed to use
  shared cache, so that the same in-memory database can be accessed from
  multiple database connections.
* Recognize and use the mode=memory query parameter in URI filenames.
* Avoid resetting the schema of shared cache connections when any one
  connection closes. Instead, wait for the last connection to close before
  reseting the schema.
* In the RTREE extension, when rounding 64-bit floating point numbers to 32-bit
  for storage, always round in a direction that causes the bounding box to get
* Adjust the unix driver to avoid unnecessary calls to fchown().
* Add interfaces sqlite3_quota_ferror() and sqlite3_quota_file_available() to
  the test_quota.c module.
* The sqlite3_create_module() and sqlite3_create_module_v2() interfaces return
  SQLITE_MISUSE on any attempt to overload or replace a virtual table module.
  The destructor is always called in this case, in accordance with historical
  and current documentation.

Revision 1.10 / (download) - annotate - [select for diffs], Fri May 25 20:04:21 2012 UTC (11 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.9: +4 -4 lines
Diff to previous 1.9 (colored)

* Fix a bug in the 3.7.12 release that can cause a segfault for certain obscure
  nested aggregate queries.
* Fix various other minor test script problems.

Revision 1.9 / (download) - annotate - [select for diffs], Tue May 15 08:09:25 2012 UTC (11 years, 6 months ago) by adam
Branch: MAIN
Changes since 1.8: +4 -4 lines
Diff to previous 1.8 (colored)

Changes 3.7.12:
* Add the SQLITE_DBSTATUS_CACHE_WRITE option for sqlite3_db_status().
* Optimize the typeof() and length() SQL functions so that they avoid unnecessary reading of database content from disk.
* Add the FTS4 "merge" command, the FTS4 "automerge" command, and the FTS4 "integrity-check" command.
* Report the name of specific CHECK constraints that fail.
* In the command-line shell, use popen() instead of fopen() if the first character of the argument to the ".output" command is "|".
* Make use of OVERLAPPED in the windows VFS to avoid some system calls and thereby obtain a performance improvement.
* More aggressive optimization of the AND operator when one side or the other is always false.
* Improved performance of queries with many OR-connected terms in the WHERE clause that can all be indexed.
* Add the SQLITE_RTREE_INT_ONLY compile-time option to force the R*Tree Extension Module to use integer instead of floating point values for both storage and computation.
* Enhance the PRAGMA integrity_check command to use much less memory when processing multi-gigabyte databases.
* New interfaces added to the test_quota.c add-on module.
* Added the ".trace" dot-command to the command-line shell.
* Allow virtual table constructors to be invoked recursively.
* Improved optimization of ORDER BY clauses on compound queries.
* Improved optimization of aggregate subqueries contained within an aggregate query.
* Bug fix: Fix the RELEASE command so that it does not cancel pending queries. This repairs a problem introduced in 3.7.11.
* Bug fix: Do not discard the DISTINCT as superfluous unless a subset of the result set is subject to a UNIQUE constraint and it none of the columns in that subset can be NULL.
* Bug fix: Do not optimize away an ORDER BY clause that has the same terms as a UNIQUE index unless those terms are also NOT NULL.

Revision 1.8 / (download) - annotate - [select for diffs], Tue Mar 20 21:00:47 2012 UTC (11 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2012Q1-base, pkgsrc-2012Q1
Changes since 1.7: +4 -4 lines
Diff to previous 1.7 (colored)

Changes 3.7.11:
* Enhance the INSERT syntax to allow multiple rows to be inserted via
  the VALUES clause.
* Enhance the CREATE VIRTUAL TABLE command to support the IF NOT EXISTS clause.
* Added the sqlite3_stricmp() interface as a counterpart to sqlite3_strnicmp().
* Added the sqlite3_db_readonly() interface.
* Added the SQLITE_FCNTL_PRAGMA file control, giving VFS implementations
  the ability to add new PRAGMA statements or to override built-in PRAGMAs.
* Queries of the form: "SELECT max(x), y FROM table" returns the value of y on
  the same row that contains the maximum x value.
* Added support for the FTS4 languageid option.
* Documented support for the FTS4 content option. This feature has actually
  been in the code since version 3.7.9 but is only now considered to be
  officially supported.
* Pending statements no longer block ROLLBACK. Instead, the pending statement
  will return SQLITE_ABORT upon next access after the ROLLBACK.
* Improvements to the handling of CSV inputs in the command-line shell
* Fix a bug introduced in version 3.7.10 that might cause a LEFT JOIN to be
  incorrectly converted into an INNER JOIN if the WHERE clause indexable terms
  connected by OR.

Revision 1.7 / (download) - annotate - [select for diffs], Tue Jan 17 15:53:13 2012 UTC (11 years, 10 months ago) by adam
Branch: MAIN
Changes since 1.6: +4 -4 lines
Diff to previous 1.6 (colored)

Changes 3.7.10:
* The default schema format number is changed from 1 to 4. This means that,
  unless the PRAGMA legacy_file_format=ON statement is run, newly created
  database files will be unreadable by version of SQLite prior to 3.3.0
  (2006-01-10). It also means that the descending indices are enabled by
* The sqlite3_pcache_methods structure and the SQLITE_CONFIG_PCACHE and
  SQLITE_CONFIG_GETPCACHE configuration parameters are deprecated. They are
  replaced by a new sqlite3_pcache_methods2 structure and SQLITE_CONFIG_PCACHE2
  and SQLITE_CONFIG_GETPCACHE2 configuration parameters.
* Added the powersafe overwrite property to the VFS interface. Provide the
  SQLITE_POWERSAFE_OVERWRITE compile-time option, and the "psow=BOOLEAN" query
  parameter for URI filenames.
* Added the sqlite3_db_release_memory() interface and the shrink_memory pragma.
* Added the sqlite3_db_filename() interface.
* Added the sqlite3_stmt_busy() interface.
* Added the sqlite3_uri_boolean() and sqlite3_uri_int64() interfaces.
* If the argument to PRAGMA cache_size is negative N, that means to use
  approximately -1024*N bytes of memory for the page cache regardless of the
  page size.
* Enhanced the default memory allocator to make use of _msize() on windows,
  malloc_size() on Mac, and malloc_usable_size() on Linux.
* Enhanced the query planner to support index queries with range constraints on
  the rowid.
* Enhanced the query planner flattening logic to allow UNION ALL compounds to
  be promoted upwards to replace a simple wrapper SELECT even if the compounds
  are joins.
* Enhanced the query planner so that the xfer optimization can be used with
  INTEGER PRIMARY KEY ON CONFLICT as long as the destination table is initially
* Enhanced the windows VFS so that all system calls can be overridden using the
  xSetSystemCall interface.
* Updated the "unix-dotfile" VFS to use locking directories with mkdir() and
  rmdir() instead of locking files with open() and unlink().
* Enhancements to the test_quota.c extension to support stdio-like interfaces
  with quotas.
* Change the unix VFS to be tolerant of read() system calls that return less
  then the full number of requested bytes.
* Change both unix and windows VFSes to report a sector size of 4096 instead of
  the old default of 512.
* In the TCL Interface, add the -uri option to the "sqlite3" TCL command used
  for creating new database connection objects.
* Added the SQLITE_TESTCTRL_EXPLAIN_STMT test-control option with the
  SQLITE_ENABLE_TREE_EXPLAIN compile-time option to enable the command-line
  shell to display ASCII-art parse trees of SQL statements that it processes,
  for debugging and analysis.
* Bug fix: Add an additional xSync when restarting a WAL in order to prevent an
  exceedingly unlikely but theoretically possible database corruption following
* Bug fix: Change the VDBE so that all registers are initialized to Invalid
  instead of NULL.
* Bug fix: Fix problems that can result from 32-bit integer overflow.

Revision 1.6 / (download) - annotate - [select for diffs], Sat Nov 5 19:09:07 2011 UTC (12 years, 1 month ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2011Q4-base, pkgsrc-2011Q4
Changes since 1.5: +4 -4 lines
Diff to previous 1.5 (colored)

Changes 3.7.9:
* If a search token (on the right-hand side of the MATCH operator) in FTS4
  begins with "^" then that token must be the first in its field of the
  document. ** Potentially Incompatible Change **
  sqlite3_db_status() interface.
* Removed support for SQLITE_ENABLE_STAT2, replacing it with the much more
  capable SQLITE_ENABLE_STAT3 option.
* Enhancements to the sqlite3_analyzer utility program, including the --pageinfo
  and --stats options and support for multiplexed databases.
* Enhance the sqlite3_data_count() interface so that it can be used to determine
  if SQLITE_DONE has been seen on the prepared statement.
* Added the SQLITE_FCNTL_OVERWRITE file-control by which the SQLite core
  indicates to the VFS that the current transaction will overwrite the entire
  database file.
* Increase the default lookaside memory allocator allocation size from 100 to
  128 bytes.
* Enhanced the query planner so that it can factor terms in and out of OR
  expressions in the WHERE clause in an effort to find better indices.
* Added the SQLITE_DIRECT_OVERFLOW_READ compile-time option, causing overflow
  pages to be read directly from the database file, bypassing the page cache.
* Remove limits on the magnitude of precision and width value in the format
  specifiers of the sqlite3_mprintf() family of string rendering routines.
* Fix a bug that prevent ALTER TABLE ... RENAME from working on some virtual
  tables in a database with a UTF16 encoding.
* Fix a bug in ASCII-to-float conversion that causes slow performance and
  incorrect results when converting numbers with ridiculously large exponents.
* Fix a bug that causes incorrect results in aggregate queries that use
  multiple aggregate functions whose arguments contain complicated expressions
  that differ only in the case of string literals contained within those
* Fix a bug that prevented the page_count and quick_check pragmas from working
  correctly if their names were capitalized.
* Fix a bug that caused VACUUM to fail if the count_changes pragma was engaged.
* Fix a bug in virtual table implementation that causes a crash if an FTS4
  table is dropped inside a transaction and a SAVEPOINT occurs afterwards.

Revision 1.5 / (download) - annotate - [select for diffs], Mon Oct 3 10:22:19 2011 UTC (12 years, 2 months ago) by adam
Branch: MAIN
Changes since 1.4: +4 -4 lines
Diff to previous 1.4 (colored)

Changes 3.7.8:
* Orders of magnitude performance improvement for CREATE INDEX on very large
* Improved the windows VFS to better defend against interference from
  anti-virus software.
* Improved query plan optimization when the DISTINCT keyword is present.
* Allow more system calls to be overridden in the unix VFS - to provide better
  support for chromium sandboxes.
* Increase the default size of a lookahead cache line from 100 to 128 bytes.
* Enhancements to the test_quota.c module so that it can track preexisting
* Bug fix: Virtual tables now handle IS NOT NULL constraints correctly.
* Bug fixes: Correctly handle nested correlated subqueries used with indices in
  a WHERE clause.

Revision 1.4 / (download) - annotate - [select for diffs], Fri Jul 8 09:35:40 2011 UTC (12 years, 5 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2011Q3-base, pkgsrc-2011Q3
Changes since 1.3: +4 -4 lines
Diff to previous 1.3 (colored)

* Fix a bug causing PRAGMA case_sensitive_like statements compiled using
  sqlite3_prepare() to fail with an SQLITE_SCHEMA error.

Changes 3.7.7:
* Add support for URI filenames
* Add the sqlite3_vtab_config() interface in support of ON CONFLICT clauses
  with virtual tables.
* Add the xSavepoint, xRelease and xRollbackTo methods in virtual tables in
  support of SAVEPOINT for virtual tables.
* Update the built-in FTS3/FTS4 and RTREE virtual tables to support ON CONFLICT
  clauses and REPLACE.
* Avoid unnecessary reparsing of the database schema.
* Added support for the FTS4 prefix option and the FTS4 order option.
* Allow WAL-mode databases to be opened read-only as long as there is an
  existing read/write connection.
* Added support for short filenames.

Revision 1.3 / (download) - annotate - [select for diffs], Tue Apr 12 19:03:48 2011 UTC (12 years, 8 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2011Q2-base, pkgsrc-2011Q2
Changes since 1.2: +4 -4 lines
Diff to previous 1.2 (colored)

Updated docs for sqlite3-3.7.6

Revision 1.2 / (download) - annotate - [select for diffs], Wed Feb 2 09:03:09 2011 UTC (12 years, 10 months ago) by adam
Branch: MAIN
CVS Tags: pkgsrc-2011Q1-base, pkgsrc-2011Q1
Changes since 1.1: +4 -4 lines
Diff to previous 1.1 (colored)

Changes 3.7.5:
* Added the sqlite3_vsnprintf() interface.
  and SQLITE_DBSTATUS_LOOKASIDE_MISS_FULL options for the sqlite3_db_status()
* Added the SQLITE_OMIT_AUTORESET compile-time option.
* Added the SQLITE_DEFAULT_FOREIGN_KEYS compile-time option.
* Updates to sqlite3_stmt_readonly() so that its result is well-defined for all
  prepared statements and so that it works with VACUUM.
* Added the "-heap" option to the command-line shell
* Fix a bug involving frequent changes in and out of WAL mode and VACUUM that
  could (in theory) cause database corruption.
* Enhance the sqlite3_trace() mechanism so that nested SQL statements such as
  might be generated by virtual tables are shown but are shown in comments and
  without parameter expansion. This greatly improves tracing output when using
  the FTS3/4 and/or RTREE virtual tables.
* Change the xFileControl() methods on all built-in VFSes to return
  SQLITE_NOTFOUND instead of SQLITE_ERROR for an unrecognized operation code.
* The SQLite core invokes the SQLITE_FCNTL_SYNC_OMITTED file control to the VFS
  in place of a call to xSync if the database has PRAGMA synchronous set to OFF.

Revision / (download) - annotate - [select for diffs] (vendor branch), Mon Nov 15 20:27:06 2010 UTC (13 years ago) by dholland
Branch: TNF
CVS Tags: pkgsrc-base, pkgsrc-2010Q4-base, pkgsrc-2010Q4
Changes since 1.1: +0 -0 lines
Diff to previous 1.1 (colored)

Add a package for the sqlite3 documentation, which is shipped
separately from the main library.

Revision 1.1 / (download) - annotate - [select for diffs], Mon Nov 15 20:27:06 2010 UTC (13 years ago) by dholland
Branch: MAIN

Initial revision

This form allows you to request diff's between any two revisions of a file. You may select a symbolic revision name using the selection box or you may type in a numeric name using the type-in text box.

CVSweb <>