|Index||index by Group||index by Distribution||index by Vendor||index by creation date||index by Name||Mirrors||Help||Search|
|Name: libsqlite3-0-32bit||Distribution: openSUSE Leap 15.1|
|Version: 3.28.0||Vendor: openSUSE|
|Release: lp151.1.1||Build date: Fri May 3 21:49:45 2019|
|Group: Development/Libraries/C and C++||Build host: lamb12|
|Size: 1261636||Source RPM: sqlite3-3.28.0-lp151.1.1.src.rpm|
|Summary: Shared libraries for the Embeddable SQL Database Engine|
This package contains the shared libraries for the Embeddable SQL Database Engine. SQLite is a C library that implements an embeddable SQL database engine. Programs that link with the SQLite library can have SQL database access without running a separate RDBMS process. SQLite is not a client library used to connect to a big database server. SQLite is a server and the SQLite library reads and writes directly to and from the database files on disk. SQLite can be used via the sqlite command line tool or via any application that supports the Qt database plug-ins.
* Wed Apr 17 2019 Reinhard Max <email@example.com> - Upgrade to 3.28.0: * CVE-2019-9936, bsc#1130326: running fts5 prefix queries inside a transaction could trigger a heap-based buffer over-read. * CVE-2019-9937, bsc#1130325: interleaving reads and writes in a single transaction with an fts5 virtual table will lead to a NULL Pointer Dereference. * Enhanced window functions * Enhanced VACUUM INTO so that it works for read-only databases. * New query optimizations. * 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(). * Improved robustness against corrupt database files. * Tue Mar 19 2019 Reinhard Max <firstname.lastname@example.org> - CVE-2018-20346, bsc#1119687: Upgrade to the most recent version to fix a remote code execution vulnerability in FTS3 (Magellan). - Drop sqlite-fts5-link.patch and do it in the spec file instead. - Version 3.27.2: * Add the VACUUM INTO command * Issue an SQLITE_WARNING message on the error log if a double-quoted string literal is used * Add the remove_diacritics=2 option to FTS3 and FTS5. * Add 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 * Enhancements to the CLI, mostly to support testing and debugging of the SQLite library itself * Increased robustness against malicious SQL that is run against a maliciously corrupted database - Version 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. * Improvements to the ".help" command in the CLI. * 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 in the CLI 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. - Version 3.25.2: * Add the PRAGMA legacy_alter_table=ON command that causes the "ALTER TABLE RENAME" command to behave as in 3.24.0 and earlier * Fix issue with some expressions with windows functions in views - Version 3.25.1: * Avoid false-positive error checks on ALTER TABLE * Further ORDER BY LIMIT optimization fixes for window functions - Version 3.25.0: * Add support for window functions * Add support for renaming columns within a table * Query optimizer improvements * slightly better concurrency in multi-threaded environments * 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 - Version 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 * Add C-language APIs for dynamic strings based on sqlite3_str * 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 * 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. * Automatically intercept the raw EXPLAIN QUERY PLAN output an reformat 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 * Add the --append option to the ".backup" command * Add the ".dbconfig" command * various performance improvements * various bug fixes * Wed Apr 11 2018 email@example.com - update to 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 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 * Mon Apr 02 2018 firstname.lastname@example.org - update to 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 * Various bug fixes * Fix various issues reported by fuzzers, including: + CVE-2018-8740: NULL pointer dereference on CREATE TABLE as (bsc#1085790) * Thu Feb 01 2018 email@example.com - update to 3.22.0: * Add Zipfile virtual table to read and write a ZIP Archive. * Improved handling of WAL mode databases * various improvements, optimizations and bug fixes * Wed Oct 25 2017 firstname.lastname@example.org - Update to version 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. * Miscellaneous microoptimizations reduce CPU usage by about 2.1%. Bug fixes * Fix a faulty assert() statement discovered by OSSFuzz. Ticket cb91bf4290c211d * Fix an obscure memory leak in sqlite3_result_pointer(). Ticket 7486aa54b968e9b * Avoid a possible use-after-free error by deferring schema resets until after the query planner has finished running. Ticket be436a7f4587ce5 * Only use indexes-on-expressions to optimize ORDER BY or GROUP BY if the COLLATE is correct. Ticket e20dd54ab0e4383 * Fix an assertion fault that was coming up when the expression in an index-on-expressions is really a constant. Ticket aa98619ad08ddca * Fix an assertion fault that could occur following PRAGMA reverse_unordered_selects. Ticket cb91bf4290c211d * Fix a segfault that can occur for queries that use table-valued functions in an IN or EXISTS subquery. Ticket b899b6042f97f5 * Fix a potential integer overflow problem when compiling a particular horrendous common table expression. This was another problem discovered by OSSFuzz. Check-in 6ee8cb6ae5. * Fix a potential out-of-bound read when querying a corrupt database file, a problem detected by Natalie Silvanovich of Google Project Zero. Check-in 04925dee41a21f. * Wed Aug 30 2017 email@example.com - update to 3.20.1: * Fix a potential memory leak in the new sqlite3_result_pointer() interface * Wed Aug 02 2017 firstname.lastname@example.org - Update to 3.20.0: * Potential incompatible change for clients incorrectly relying on unspecified behavior: column names returned by sqlite3_column_name() and sqlite3_column_name16() may return different names when views or subqueries are used in the FROM clause, and AS clauses are not used (as they should be) * Text of some error messages changed. Applications that depend on specific error message text may be impacted. * Fri Jun 16 2017 email@example.com - a little less packaging cleanup so as to not break SLE 11 SP4 * Fri Jun 16 2017 firstname.lastname@example.org - Small packaging cleanup * Fri Jun 09 2017 email@example.com - Update to 3.19.3: * Fix a bug associated with auto_vacuum that can lead to database corruption. (introduced in 3.16.0) * Thu May 25 2017 firstname.lastname@example.org - Update to 3.19.2 * Fix a bug in the LEFT JOIN flattening optimization. Ticket cad1ab4cb7b0fc. * Fix more bugs in the LEFT JOIN flattening optimization. Ticket 7fde638e94287d2c. * Mon May 22 2017 email@example.com - Update to 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. * Fix a problem in REPLACE that can result in a corrupt database containing two ore more rows with the same rowid. Fix for ticket f68dc596c4e6018d. * Fix a problem in PRAGMA integrity_check that was causing a subsequent VACUUM to behave suboptimally. so that it works correctly with foreign keys on WITHOUT ROWID tables. * Disallow leading zeros in numeric constants in JSON. Fix for ticket b93be8729a895a528e2. * Disallow control characters inside of strings in JSON. Fix for ticket 6c9b5514077fed34551. * Limit the depth of recursion for JSON objects and arrays in orde to avoid excess stack usage in the recursive descent parser. Fix for ticket 981329adeef51011052. * Fri Mar 31 2017 firstname.lastname@example.org - Update to 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. * 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. * Wed Feb 15 2017 email@example.com - Drop update-desktop-files BuildRequires: this package contains no desktop files, hence there is no need to handle any of them. * Tue Feb 14 2017 firstname.lastname@example.org - Update to 3.17.0 * Approximately 25% better performance from the R-Tree extension. * 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. * Use compiler built-ins __builtin_sub_overflow(), __builtin_add_overflow(), and __builtin_mul_overflow() when available. * 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. * 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. Fix for ticket 25e335f802dd. * Use the correct affinity for columns of automatic indexes. Ticket 7ffd1ca1d2ad4ec. * Ensure that the sqlite3_blob_reopen() interface can correctly handle short rows. Fix for ticket e6e962d6b0f06f46e. * Sat Jan 07 2017 email@example.com - Update to version 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. * Fix the sqlite3_value_text() interface so that it correctly translates content generated by zeroblob() into a string of all 0x00 characters. * 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. * 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. * Tue Jan 03 2017 firstname.lastname@example.org - Update to version 3.16.1 * Fix a bug concerning the use of row values within triggers (see ticket 8c9458e7) that was in version 3.15.0. * Tue Jan 03 2017 email@example.com - Update to version 3.16.0: * 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. * Fri Dec 30 2016 firstname.lastname@example.org - SQLite 3.15.2: * Multiple bug fixes to the row value logic that was introduced in version 3.15.0. * Fix a NULL pointer dereference in ATTACH/DETACH following a maliciously constructed syntax error * Fix a crash that can occur following an out-of-memory condition in the built-in instr() function. * In the JSON extension, fix the JSON validator so that it correctly rejects invalid backslash escapes within strings. * Mon Nov 21 2016 email@example.com - SQLite 3.15.1: * 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 * Fix a case 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 * Fri Oct 14 2016 firstname.lastname@example.org - SQLite 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 support for SQLITE_DBCONFIG_MAINDBNAME. * 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()). * The multiply operator now correctly detects 64-bit integer overflow and promotes to floating point in all corner-cases. Fix for ticket 1ec41379c9c1e400. * Correct handling of columns with redundant unique indexes when those columns are used on the LHS of an IN operator. Fix for ticket 0eab1ac759. * Skip NULL entries on range queries in indexes on expressions. Fix for ticket 4baa46491212947. * Ensure that the AUTOINCREMENT counters in the sqlite_sequence table are initialized doing "Xfer Optimization" on "INSERT ... SELECT" statements. Fix for ticket 7b3328086a5c116c. * Make sure the ORDER BY LIMIT optimization (from check-in 559733b09e) works with IN operators on INTEGER PRIMARY KEYs. Fix for ticket 96c1454c * Wed Sep 14 2016 email@example.com - SQLite 3.14.2: * 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. Fix for ticket 199df4168c. * 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. Ticket ef360601 * Sun Aug 14 2016 firstname.lastname@example.org - SQLite 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. * Mon Aug 08 2016 email@example.com - SQLite 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. * 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. * 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. * Fix the ALTER TABLE command so that it does not corrupt descending indexes when adding a column to a legacy file format database. Ticket f68bf68513a1c15f * Fix a NULL-pointer dereference/crash that could occurs when a transitive WHERE clause references a non-existent collating sequence. Ticket e8d439c77685eca6. * 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. * Tue Aug 02 2016 firstname.lastname@example.org - Fix SLE 11 for previous change: noarch subpackages not supported * Tue Aug 02 2016 email@example.com - Reduce the conditions a bit and sort with spec-cleaner - Remove condition for old sle10 ppc machines * Wed May 18 2016 firstname.lastname@example.org - SQLite 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 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. * 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. * Tue Apr 19 2016 email@example.com - SQLite 3.12.2: * Fix compatibility with some legacy versions of sqlite database * Minor bugfixes * Sat Apr 09 2016 firstname.lastname@example.org - SQLite 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. * Wed Mar 30 2016 email@example.com - SQLite 3.12.0: * 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. * 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. * 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. * Make sure the sqlite3_set_auxdata() values from multiple triggers within a single statement do not interfere with one another. Ticket dc9b1c91. * Fix the code generator for expressions of the form "x IN (SELECT...)" where the SELECT statement on the RHS is a correlated subquery. - Remove sqlite3-link-binary-with-libsqlite3.patch: replaced with configure option --disable-static-shell * Fri Mar 25 2016 firstname.lastname@example.org - Enable secure delete by default, this matches Fedora & Android. It can be disabled with `PRAGMA SECURE_DELETE = 0;` - Enable more extensions, syncing with Fedora & Gentoo. * Mon Mar 07 2016 email@example.com - Fix sqlite-fts5-link.patch: link libsqlite3.so with libm instead of the sqlite3 binary: the library is the actual user of log(). - Add sqlite3-link-binary-with-libsqlite3.patch: dyamically link /usr/bin/sqlite3 to libsqlite3 instead of statically using it. - Move autoreconf call to build section, where it belongs. * Mon Mar 07 2016 firstname.lastname@example.org - Enable FTS5 support. - Add sqlite-fts5-link.patch to link to math library because FTS5 code uses log(). * Fri Mar 04 2016 email@example.com - SQLite 3.11.1: * 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. * Tue Mar 01 2016 firstname.lastname@example.org - explicitly enable readline support - run spec-cleaner * Thu Feb 18 2016 email@example.com - Update to 3.11.0 * 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. * 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. * Wed Jan 20 2016 firstname.lastname@example.org - SQlite 3.10.2: * Fix case-folding bug introduced in 3.10.0 in the LIKE operator * 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. * Fri Jan 15 2016 email@example.com - SQLite 3.10.1: * 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. * Add SQLITE_FCNTL_JOURNAL_POINTER file control * Thu Jan 07 2016 firstname.lastname@example.org - update to 3.10.0 - spec-cleaned * 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. + Enhancements to the command-line shell: * Added the ".changes ON|OFF" and ".vfsinfo" dot-commands. + 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. * Fix an infinite-loop in the query planner that could occur on malformed common table expressions. * Various bug fixes in the sqldiff tool. * Mon Nov 02 2015 email@example.com - SQLite 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. * Fri Oct 16 2015 firstname.lastname@example.org - SQLite 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. * Build and portability fixes. * Thu Oct 15 2015 email@example.com - SQLite 3.9.0 * Add json1 extension module * 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 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. * sqlite3_memory_alarm() no-op. * Fri Jul 31 2015 firstname.lastname@example.org - Update to 184.108.40.206 * 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. * Mon Jul 27 2015 email@example.com - SQLite 3.8.11: * Significantly improved performance * new interfaces and enhancements * Important bug fixes for CREATE TABLE AS * Fix the skip-scan optimization so that it works correctly when the OR optimization is used on WITHOUT ROWID tables. * Fix the sqlite3_memory_used() and sqlite3_memory_highwater() interfaces so that they actually do provide a 64-bit answer. * experimental extensions, not enabled: + RBU (Resumable Bulk Update) extension + FTS5 (Full-text search) extension * Sun May 24 2015 firstname.lastname@example.org - SQLite 220.127.116.11: * Fix an index corruption issue introduced by version 3.8.7. * Sun May 10 2015 email@example.com - SQLite 18.104.22.168: * Make sqlite3_compileoption_used() responsive to the SQLITE_ENABLE_DBSTAT_VTAB compile-time option. * Fix minor issues with the dbstat virtual table. * Thu May 07 2015 firstname.lastname@example.org - Update to SQLite 3.8.10 * 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. * 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. * Wed Apr 08 2015 email@example.com - Update to SQLite 3.8.9: * 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. * Wed Feb 25 2015 firstname.lastname@example.org - Update to SQLite 22.214.171.124 * 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. * Thu Feb 12 2015 email@example.com - SQLite 126.96.36.199: * Enhance sqlite3_wal_checkpoint_v2(TRUNCATE) interface so that it truncates the WAL file even if there is no checkpoint work to be done. * Tue Jan 20 2015 firstname.lastname@example.org - SQLite 188.8.131.52: * 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. * Fri Jan 16 2015 email@example.com - SQLite 3.8.8 - New Features: * Added the PRAGMA data_version command * Added the SQLITE_CHECKPOINT_TRUNCATE option to the sqlite3_wal_checkpoint_v2() / PRAGMA wal_checkpoint. * Added the sqlite3_stmt_scanstatus() 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() * 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. - 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. * Thu Dec 11 2014 firstname.lastname@example.org - SQLite 184.108.40.206: * Bug fix: Add in a mutex that was omitted from the previous release. * Sat Dec 06 2014 email@example.com - SQLite 220.127.116.11: * 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. * 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. * Wed Nov 19 2014 firstname.lastname@example.org - SQLite 18.104.22.168: * Enhance the ROLLBACK command so that pending queries are allowed to continue as long as the schema is unchanged. * Bug fix: Make sure that NULL results from OP_Column are fully and completely NULL and do not have the MEM_Ephem bit set. * Bug fix: The %c format in sqlite3_mprintf() is able to handle precisions greater than 70. * Bug fix: Do not automatically remove the DISTINCT keyword from a SELECT that forms the right-hand side of an IN operator since it is necessary if the SELECT also contains a LIMIT. * Wed Oct 29 2014 email@example.com - SQLite 22.214.171.124: * 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. * Fri Oct 17 2014 firstname.lastname@example.org - SQLite 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 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() 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. - Test, Debug, and Analysis Changes: * Show ASCII-art abstract syntax tree diagrams using the ".selecttrace" and ".wheretrace" commands in the command-line shell when compiled with SQLITE_DEBUG, SQLITE_ENABLE_SELECTTRACE, and SQLITE_ENABLE_WHERETRACE. Also provide the sqlite3TreeViewExpr() and sqlite3TreeViewSelect() entry points that can be invoked from with the debugger to show the parse tree when stopped at a breakpoint. * Drop support for SQLITE_ENABLE_TREE_EXPLAIN. The SELECTTRACE mechanism provides more useful diagnostics information. * New options to the command-line shell for configuring auxiliary memory usage: --pagecache, --lookaside, and --scratch.
Generated by rpm2html 1.8.1
Fabrice Bellet, Tue Nov 9 09:58:45 2021