{"id":123615,"date":"2025-04-20T09:05:07","date_gmt":"2025-04-20T07:05:07","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-subd-mysql-9-3-0"},"modified":"2025-04-20T09:05:07","modified_gmt":"2025-04-20T07:05:07","slug":"vypusk-subd-mysql-9-3-0","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-subd-mysql-9-3-0","title":{"rendered":"Release of the MySQL Database Management System 9.3.0","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
Oracle has launched a new branch of the MySQL database management system, version 9.3.0. Releases of MySQL Community Server 9.3.0 have been prepared for all major distributions of Linux, FreeBSD, macOS, and Windows. According to the new release model implemented in 2023, MySQL 9.3 is classified under the 'Innovation' branches. Innovation branches are recommended for those who want earlier access to new functionalities, are published every 3 months, and are supported only until the next major release is published (for example, support for branch 9.2 ended after the emergence of branch 9.3). In the summer, they plan to create an LTS release 9.4, recommended for implementations that require predictability and long-term maintenance of unchanged behavior. Following the LTS branch, a new Innovation branch will be formed \u2014 MySQL 10.0. <\/p>\n
Key changes in MySQL 9.3: <\/p>\n
\n
The mysqldump utility has added the option '--users' for creating logical dumps with information about all accounts, output via SQL statements 'CREATE USER' and 'GRANT'. To include the 'DROP USER' statement before 'CREATE USER', the option '--add-drop-user' is provided, and to selectively reflect individual users in the dump \u2014 the options '--include-user=user@host' and '--exclude-user=user@host', which can be specified multiple times.\n
In the MLE (Multilingual Engine Component), which allows the use of code in languages other than SQL within stored procedures and functions, support for JavaScript has been improved. For stored procedures in JavaScript, a 'DECIMAL' type has been implemented, which can be used for input and return arguments. By default, for security reasons, the MySQL DECIMAL type is converted to the JavaScript 'String' type, but this behavior can be overridden with the command 'SELECT mle_set_session_state('{'decimal_type':'Number'})'', after which the JavaScript 'Number' type will be used. Conversions to the DECIMAL type are supported for JavaScript types Boolean, Number, String, and BigInt.\n
Support for setting localization parameters has been added to JavaScript stored procedures using the JavaScript API Intl. For example, to determine the current locale, the property 'Intl.DateTimeFormat().resolvedOptions().locale' can be used, and to override the locale \u2014 the method 'toLocaleString()'.\n
Enhanced capabilities for managing JavaScript libraries: the expressions «ALTER PROCEDURE» and «ALTER FUNCTION» can now be used to modify the list of imported libraries. The expression «ALTER LIBRARY» has been added to allow for the addition, deletion, or modification of SQL comments for the library. The expression «SHOW LIBRARY STATUS» has been implemented to obtain information about the library.\n
Support for dynamic loading of JavaScript libraries has been added. To dynamically import a library, the «await» keyword should be used, for example «let module = await import(‘\\\/db1\\\/lib_${object_type}’)».\n
Optimizations for queries using quantified comparison operators have been enhanced. In addition to supporting the operators «=ANY» and «<>ALL», the new version now supports the operators «>ANY», «>=ANY», «<ANY», «<=ANY», «>ALL», «>=ALL», «<ALL», and «<=ALL» when optimizing subqueries.\n
The «version_tokens» plugin, which was previously marked as deprecated, has been removed.\n
Setting the value 0 in the system variable replica_parallel_workers is prohibited.\n
28 vulnerabilities have been resolved, of which 26 can be exploited remotely with access to submit queries to the database management system. The six most serious issues have a severity level of 6.5 and are related to vulnerabilities in the InnoDB engine, parser, and optimizer. Less severe vulnerabilities affect mysqldump, InnoDB, optimizer, DDL, UDF, parser, and the replication system. <\/ul>\n