Small. Fast. Reliable.
Choose any three.

## SQLite Release 3.49.1 On 2025-02-18

Prior changes from version 3.49.0 (2025-02-06):

1. Enhancements to the query planner:
   1. Improve the query-time index optimization so that it works on WITHOUT ROWID tables.
   2. Better query plans for large star-query joins. This fixes three different performance regressions that were reported on the SQLite Forum.
   3. When two or more queries have the same estimated cost, use the one with the fewer bytes per row.
2. Enhance the iif() SQL function so that it can accept any number of arguments greater than or equal to two.
3. Enhance the session extension so that it works on databases that make use of generated columns.
4. Omit the SQLITE_USE_STDIO_FOR_CONSOLE compile-time option which was not implemented correctly and never worked right. In its place add the SQLITE_USE_W32_FOR_CONSOLE_IO compile-time option. This option applies to command-line tools like the CLI only, not to the SQLite core. It causes Win32 APIs to be used for console I/O instead of stdio. This option affects Windows builds only.
5. Three new options to sqlite3_db_config(). All default to "on".
   1. SQLITE_DBCONFIG_ENABLE_ATTACH_CREATE
   2. SQLITE_DBCONFIG_ENABLE_ATTACH_WRITE
   3. SQLITE_DBCONFIG_ENABLE_COMMENTS
6. Replace Autotools with Autosetup for the configure script used in the precompiled amalgamation tarball. The configure script for the canonical source code was changed to Autosetup in the previous (3.48.0) release. Only the main SQLite configure script in the amalgamation tarball is changed. The (deprecated) configuration script use by TEA subdirectory of the amalgamation tarball still relies on Autotools.
7. Various minor patches and fixes for problems seen in the 3.48.0 release.

Changes in this specific patch release, version 3.49.1 (2025-02-18):

1. Improve portability of makefiles and configure scripts.
2. Fix a bug in the concat_ws() function, introduced in version 3.44.0, that could lead to a memory error if the separator string is very large (hundreds of megabytes).
3. Enhanced the SQLITE_DBCONFIG_LOOKASIDE interface to make it more robust against misuse.

   Hashes:

4. SQLITE_SOURCE_ID: 2025-02-18 13:38:58 873d4e274b4988d260ba8354a9718324a1c26187a4ab4c1cc0227c03d0f10e70
5. SHA3-256 for sqlite3.c: 22eab05c842463a3705c63922f12f68531200185ced510ed6aed2065ca44e816

A complete list of SQLite releases in a single page and a chronology are both also available. A detailed history of every check-in is available at SQLite version control site.