{"id":116050,"date":"2024-05-24T08:59:21","date_gmt":"2024-05-24T06:59:21","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-subd-sqlite-3-46"},"modified":"2024-05-24T08:59:21","modified_gmt":"2024-05-24T06:59:21","slug":"vypusk-subd-sqlite-3-46","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-subd-sqlite-3-46","title":{"rendered":"Release of SQLite DBMS 3.46","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
SQLite 3.46 has been released, a lightweight database management system presented as a shared library. The SQLite code is released into the public domain, meaning it can be used without restrictions and free of charge for any purpose. Financial support for SQLite developers is provided by a specially created consortium. <\/p>\n
Key Changes: <\/p>\n
\n
The ability to use the separator \u2018_\u2019 in numbers has been provided for a clearer representation of numerical literals (e.g., 1_234_567).\n
A new SQL function json_pretty() has been introduced to generate more readable output in JSON format, formatted using indentation for block highlighting.\n
The capabilities of the \u2018PRAGMA optimize\u2019 operation, which performs database optimization and data schema optimization for better query performance, have been expanded. A limit on the duration of database analysis has been implemented, excluding excessive processing time for large databases. A new bitmask \u2018PRAGMA optimize(0x10000)\u2019 has been added for separate updates checking across all tables. Automatic re-analysis of tables without records in sqlite_stat1 has been ensured.\n
Support for substitutions %G, %g, %U, and %V has been added to the SQL function strftime().\n
New modifiers ceiling and floor have been added to SQL functions for date and time handling to manage ambiguous dates that arise when shifting dates by a set number of months or years. Modifiers utc and localtime are ignored if SQLite knows that the time is already in UTC or localtime representation.\n
Optimizations have been made in the query planner. For INSERT expressions containing thousands of values in the VALUES section, the \u2018VALUES-as-coroutine\u2019 optimization is enabled by default, allowing for approximately double the parsing speed of such expressions and halving memory consumption. For queries like \u2018SELECT count(DISTINCT col) FROM ...\u2019, the use of indexes is permitted even if the size of records in the index is no less than that in the table. The logic for determining situations where constants are specified in SQL function arguments has been improved. Push-down optimization for WHERE expressions containing unrelated subqueries has been applied.\n
The logic for handling stack overflow has been changed \u2014 upon detecting insufficient memory for the stack, the parser now attempts to allocate additional memory from the heap instead of throwing a \u2018parser stack overflow\u2019 error.\n
In JSON, control characters are now allowed in JSON5 string literals. The logic of the operators \u2018->\u2019 and \u2018->>\u2019 has been changed, so when the right operand is a string containing only digits, these operands are now treated as strings, similar to PostgreSQL.\n
In the DEFAULT value for table columns, large hexadecimal literals are now permitted. <\/ul>\n