Opened 2 months ago

Closed 2 months ago

#20931 closed enhancement (fixed)

sqlite-autoconf-3480000 (3.48.0)

Reported by: Bruce Dubbs Owned by: Douglas R. Reno
Priority: normal Milestone: 12.3
Component: BOOK Version: git
Severity: normal Keywords:
Cc:

Description

New minor version.

Change History (3)

comment:1 by Douglas R. Reno, 2 months ago

Owner: changed from blfs-book to Douglas R. Reno
Status: newassigned

comment:2 by Douglas R. Reno, 2 months ago

SQLite Release 3.48.0 On 2025-01-14

    Refactor the "configure" script used to help build SQLite from canonical sources, to 
fix bugs, improve performance, and make the code more maintainable.
        This does not affect the "configure" script in the sqlite3-autoconf-
NNNNNNN.tar.gz "amalgamation tarball", only the canonical sources. The build system for 
the amalgamation tarball is unchanged. If you are using the amalgamation tarball, 
nothing about this change log entry applies to you.
        The key innovation here is that Autosetup is now used instead of GNU Autoconf. 
That seems like a big change, but it is really just an implementation detail. The ./
configure script is coded very differently, but should work the same as before.
        One advantage of the new configure is that you no longer need to install TCL in 
order to build most SQLite targets. TCL is still required to run tests or to build 
accessory programs (like sqlite3_analyzer) that use TCL, but it is not required for most 
common targets. Hence, as of this release, the only build dependencies are a C compiler 
and "make" or "nmake". 
    Improved EXPLAIN QUERY PLAN output for covering indexes.
    Allow a two-argument version of the iif() SQL function. Also allow if() as an 
alternative spelling for iif().
    Add the ".dbtotxt" command to the CLI.
    Add the SQLITE_IOCAP_SUBPAGE_READ property to the xDeviceCharacteristics method of 
the sqlite3_io_methods object.
    Add the SQLITE_PREPARE_DONT_LOG option to sqlite3_prepare_v3() that prevents warning 
messages being sent to the error log if the SQL is ill-formed. This allows 
sqlite3_prepare_v3() to be used to do test compiles of SQL to check for validity without 
polluting the error log with false messages.
    Increase the minimum allowed value of SQLITE_LIMIT_LENGTH from 1 to 30.
    Added the SQLITE_FCNTL_NULL_IO file control.
    Extend the FTS5 auxiliary API xInstToken() to work with prefix queries via the 
insttoken configuration option and the fts5_insttoken() SQL function.
    Increase the maximum number of arguments to an SQL function from 127 to 1000.
    Remove vestigial traces of SQLITE_USER_AUTHENTICATION.
    Various obscure bug fixes. 

Note that the configure script changes don't affect us since we use the autoconf tarball

comment:3 by Douglas R. Reno, 2 months ago

Resolution: fixed
Status: assignedclosed
Note: See TracTickets for help on using tickets.