openSUSE Build Service

Overview Repositories Revisions Requests Users Attributes Meta

Revisions of sqlite3

Ana Guerrero (anag+factory) accepted request 1169661 from

Reinhard Max (rmax) 13 days ago (revision 151)

- Update to release 3.45.3:
  * Fix a long-standing bug (going back to version 3.24.0) that
    might (rarely) cause the "old.*" values of an UPDATE trigger
    to be incorrect if that trigger fires in response to an UPSERT.
  * Reduce the scope of the NOT NULL strength reduction
    optimization that was added as item 8e in version 3.35.0. The
    optimization was being attempted in some contexts where it did
    not work, resulting in incorrect query results.
- Add SQLITE_STRICT_SUBTYPE=1 as recommended by upstream.

Ana Guerrero (anag+factory) accepted request 1158281 from

Reinhard Max (rmax) about 2 months ago (revision 150)

- Update to release 3.45.2:
  * Added the SQLITE_RESULT_SUBTYPE property for application-
    defined SQL functions.
  * Enhancements to the JSON SQL functions
  * Add the FTS5 tokendata option to the FTS5 virtual table.
  * The SQLITE_DIRECT_OVERFLOW_READ optimization is now enabled by
    default.
  * Query planner improvements
  * Increase the default value for SQLITE_MAX_PAGE_COUNT from
    1073741824 to 4294967294.
  * Enhancements to the CLI
  * Restore the JSON BLOB input bug, and promise to support the
    anomaly in subsequent releases, for backward compatibility.
  * Fix the PRAGMA integrity_check command so that it works on
    read-only databases that contain FTS3 and FTS5 tables.
  * Fix issues associated with processing corrupt JSONB inputs.
  * Fix a long-standing bug in which a read of a few bytes past the
    end of a memory-mapped segment might occur when accessing a
    craftily corrupted database using memory-mapped database.
  * Fix a long-standing bug in which a NULL pointer dereference
    might occur in the bytecode engine due to incorrect bytecode
    being generated for a class of SQL statements that are
    deliberately designed to stress the query planner but which
    are otherwise pointless.
  * Fix an error in UPSERT, introduced in version 3.35.0.
  * Reduce the scope of the NOT NULL strength reduction
    optimization that was added in version 3.35.0.
- Add sqlite3-float-i586.patch to fix build on i586.
- sqlite3-rtree-i686.patch is not needed anymore.
- Abort build when %version and %tarversion don't match.

Ana Guerrero (anag+factory) accepted request 1133118 from

Factory Maintainer (factory-maintainer) 5 months ago (revision 149)

Automatic submission by obs-autosubmit

Ana Guerrero (anag+factory) accepted request 1130837 from

Factory Maintainer (factory-maintainer) 5 months ago (revision 148)

Automatic submission by obs-autosubmit

Ana Guerrero (anag+factory) accepted request 1123976 from

Reinhard Max (rmax) 6 months ago (revision 147)

Ana Guerrero (anag+factory) accepted request 1119230 from

Reinhard Max (rmax) 7 months ago (revision 146)

- sqlite3-rtree-i686.patch: temporary build fix for 32-bit x86.

- Update to: 3.43.2:
  * 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.

- Update 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.

- Update to 3.43.0:
  * 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.

Dominique Leuenberger (dimstar_suse) accepted request 1087547 from

Reinhard Max (rmax) 12 months ago (revision 145)

- Update to 3.42.0:
  * 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().
  * New sqlite3_db_config() options:
    SQLITE_DBCONFIG_STMT_SCANSTATUS and
    SQLITE_DBCONFIG_REVERSE_SCANORDER.
  * Query planner improvements.
  * Add the --unsafe-testing command-line option.
  * 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.
  * 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
  * 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.

Dominique Leuenberger (dimstar_suse) accepted request 1073837 from

Reinhard Max (rmax) about 1 year ago (revision 144)

- Update to 3.41.2:
  * Multiple fixes for reads past the end of memory buffers
  * 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 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.

- Update to 3.41.1:
  * 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

Dominique Leuenberger (dimstar_suse) accepted request 1071411 from

Martin Pluskal (pluskalm) about 1 year ago (revision 143)

Dominique Leuenberger (dimstar_suse) accepted request 1067149 from

Reinhard Max (rmax) about 1 year ago (revision 142)

- Update to 3.41.0:
  * https://www.sqlite.org/releaselog/3_41_0.html
  * Various query planner improvements.
  * 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.
  * In-memory databases created using sqlite3_deserialize() now
    report their filename as an empty string, not as 'x'.
  * The ".scanstats est" command provides query planner estimates
    in profiles.
  * Enhance the --safe command-line option to disallow dangerous
    SQL functions.
  * The double-quoted string misfeature is now disabled by default
    for CLI builds.
  * Various other improvements and performance enhancements.
- The new version obsoletes sqlite-src-3390000-func7-pg-181.patch

Dominique Leuenberger (dimstar_suse) accepted request 1056142 from

Martin Pluskal (pluskalm) over 1 year ago (revision 141)

Dominique Leuenberger (dimstar_suse) accepted request 1043393 from

Reinhard Max (rmax) over 1 year ago (revision 140)

- bsc#1206337, CVE-2022-46908, sqlite-CVE-2022-46908.patch:
  relying on --safe for execution of an untrusted CLI script

Dominique Leuenberger (dimstar_suse) accepted request 1037900 from

Factory Maintainer (factory-maintainer) over 1 year ago (revision 139)

Automatic submission by obs-autosubmit

Dominique Leuenberger (dimstar_suse) accepted request 1033127 from

Reinhard Max (rmax) over 1 year ago (revision 138)

Dominique Leuenberger (dimstar_suse) accepted request 1004661 from

Factory Maintainer (factory-maintainer) over 1 year ago (revision 137)

Automatic submission by obs-autosubmit

Dominique Leuenberger (dimstar_suse) accepted request 1001301 from

Reinhard Max (rmax) over 1 year ago (revision 136)

- update to 3.39.3:
  * 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.
  * Use a mutex to protect the PRAGMA temp_store_directory and
    PRAGMA data_store_directory statements, even though they are
    decremented and documented as not being threadsafe.