MySQL Database 8.2.0 is available

Oracle has formed a new branch of MySQL 8.2 and has released corrective updates for MySQL 8.0.35 and 5.7.44. The MySQL Community Server 8.2.0 builds are prepared for all major distributions of Linux, FreeBSD, macOS, and Windows.

MySQL 8.2.0 is the second release created under the new release development model, which includes two types of MySQL branches — 'Innovation' and 'LTS'. The Innovation branches, which include MySQL 8.1 and 8.2, are recommended for those who wish to access new features sooner. These branches are published every 3 months and are supported only until the next significant release is published (for example, support for branch 8.1 ends after the 8.2 branch is released). LTS branches are recommended for deployments that require predictability and long-term preservation of consistent behavior. LTS branches will be released every two years and supported in a standard mode for 5 years, in addition to which 3 years of extended support can be obtained. The LTS release of MySQL 8.4 is expected in Spring 2024, after which a new Innovation branch 9.0 will be formed.

Key changes in MySQL 8.2:

• Support for the Webauthn (FIDO2) authentication mechanism has been added, enabling multi-factor authentication and passwordless connections to server MySQL using FIDO2-compliant hardware tokens or biometric authentication. The Webauthn support plugin is currently available only for MySQL Enterprise.
• The mysql_native_password server plugin providing password-based authentication has been moved to the optional category and can be disabled. Instead of mysql_native_password, it is recommended to switch to using the caching_sha2_password plugin, which uses the SHA2 algorithm for hashing instead of SHA1. To switch users to the caching_sha2_password plugin with a random password replacement, the command can be used: ALTER USER 'username'@'localhost' IDENTIFIED WITH caching_sha2_password BY RANDOM PASSWORD PASSWORD EXPIRE FAILED_LOGIN_ATTEMPTS 3 PASSWORD_LOCK_TIME 2;
• Optimization of hash tables has been carried out, allowing faster execution of EXCEPT and INTERSECT operations.
• Debugging capabilities have been expanded. In the SELECT, INSERT, REPLACE, UPDATE, and DELETE operations, support for the 'EXPLAIN FORMAT=JSON' expression has been added to generate diagnostic output in JSON format (for example, 'EXPLAIN FORMAT=JSON INTO @var select_stmt;').
• The expression 'EXPLAIN FOR SCHEMA' has been added for outputting diagnostics related only to a specific data schema.
• An option ‘—output-as-version’ has been added to the mysqldump utility to create dumps compatible with a specific older version of MySQL (for example, BEFORE_8_2_0 or BEFORE_8_0_23 can be specified to revert the politically incorrect terminology master/slave, which has been deprecated in releases 8.2.0 and 8.0.23).
• The client C library has been updated to include the use of named attributes in parameterized queries (prepared statements) implemented through the new function mysql_stmt_bind_named_param(), replacing the function mysql_stmt_bind_param().
• SQL traffic distribution in the MySQL server cluster has been simplified. Capabilities have been provided to organize transparent connections for applications to secondary or primary servers.
• A new privilege SET_ANY_DEFINER has been added, granting the right to create objects with the DEFINER expression, as well as the privilege ALLOW_NONEXISTENT_DEFINER to protect objects without an owner.
• The following have been deprecated: the old and new variables, the masks ‘%’ and ‘_’ in database access grant operations, the option ‘—character-set-client-handshake’, the variable binlog_transaction_dependency_tracking, and the privilege SET_USER_ID.
• As part of adjustments to politically incorrect terminology related to replication, the expressions ‘RESET MASTER’, ‘SHOW MASTER STATUS’, ‘SHOW MASTER LOGS’, and ‘PURGE MASTER LOGS’ have been deprecated and should be replaced with ‘RESET BINARY LOGS AND GTIDS’, ‘SHOW BINARY LOG STATUS’, ‘SHOW BINARY LOGS’, and ‘PURGE BINARY LOGS’.
• Capabilities previously marked as deprecated have been removed: the function WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS(), the variable expire_logs_days, and the options ‘—abort-slave-event-count’ and ‘—disconnect-slave-event-count’.
• 26 vulnerabilities have been resolved. Two vulnerabilities related to the use of the Curl package and the OpenSSL library may be exploited remotely.

Source: opennet.ru