{"id":111250,"date":"2023-11-02T03:10:48","date_gmt":"2023-11-02T01:10:48","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-subd-sqlite-3-44"},"modified":"2023-11-02T03:10:48","modified_gmt":"2023-11-02T01:10:48","slug":"vypusk-subd-sqlite-3-44","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-subd-sqlite-3-44","title":{"rendered":"Release of Database Management System SQLite 3.44","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
The release of SQLite 3.44 has been published, a lightweight DBMS presented as a dynamic library. SQLite code is released into the public domain, meaning it can be used freely and without restrictions for any purpose. Financial support for the SQLite developers is provided by a specially created consortium that includes companies like Bentley, Bloomberg, Expensify, and Navigation Data Standard. <\/p>\n
Key Changes: <\/p>\n
\n
In aggregate functions, it is now allowed to specify the expression 'ORDER BY' after the last parameter to process function arguments in a specified order, which can be useful for functions like string_agg() and json_group_array().\n
Support has been added for the scalar SQL functions concat() and concat_ws(), compatible with PostgreSQL, MS SQL Server, and MySQL.\n
Support for the aggregate function string_agg(), compatible with PostgreSQL and MS SQL Server, has been added.\n
The SQL function strftime() has added support for the specifiers '%e', '%F', '%I', '%k', '%l', '%p', '%P', '%R', '%T', and '%u'.\n
The output of many errors related to the 'CREATE TABLE' expression is now displayed after executing the 'CREATE TABLE' expression, rather than after the first use of the table.\n
The 'PRAGMA integrity_check' command has implemented a consistency check of the contents of various built-in virtual tables used in FTS3, FTS4, FTS5, RTREE, and GEOPOLY extensions.\n
Built-in virtual tables used in the FTS3, FTS4, FTS5, RTREE, and GEOPOLY extensions are now allowed to be used within triggers.\n
When specifying the SQLITE_DBCONFIG_DEFENSIVE setting, protection against enabling the 'PRAGMA writable_schema' mode is ensured.\n
The SQLITE_USE_SEH (Structured Exception Handling) setting is enabled by default when compiled with Microsoft C.\n
Optimizations in the query planner have been made regarding partial index scanning when a constant value is specified in the WHERE clause for a table column. Due to identified regressions, the view scanning optimization added in version 3.42.0 has been disabled.\n
A runtime check for system support of the 'long double' type with greater precision than the 'double' type has been implemented.\n
In the Windows command interface, UTF-8 encoding is used by default for input and output (an option '--no-utf8' is available to disable this). <\/ul>\n