Changes in MySQL 8.0.42 (2025-04-15; General Availability)$$$Audit Log Notes$$$Compilation Notes$$$SQL Function and Operator Notes$$$INFORMATION_SCHEMA Notes$$$Functionality Added or Changed$$$Bugs Fixed$$$Audit Log Notes$$$<COMMAND_CLASS> was not populated for <NAME>Execute</NAME>.$$$For more information; see Logging Specific Event Classes. (Bug #36686351)$$$Compilation Notes$$$Group Replication: The OpenSSL Engine interface is deprecated; and is no longer being included in OpenSSL v3 main packages by some Linux distributions; including Fedora.$$$To avoid build issues; the usage of the OpenSSL Engine interface by the Group Communication System (GCS) is now restricted to OpenSSL versions previous to 1.1. (Bug #37475769)$$$Linux: Use /usr/bin/gcc (GCC 14.2.1) when building the server on Oracle Linux 10. (Bug #37616148)$$$Upgraded the bundled Curl library to version 8.12.1. (Bug #37633587)$$$Abseil could not be built on FreeBSD. (Bug #37611924)$$$In order to use xxhash functions independently from the lz4 library (bundled or source); we compiled xxhash.c into our own binaries; which required using a great many CMake directives. Instead; we now build an interface library for xxhash; and link with that wherever such functions are used. (Bug #37417386)$$$Use xxHash-0.8.2 from GitHub rather than the version bundled with lz4. (Bug #37387318)$$$SQL Function and Operator Notes$$$Important Change: When an SQL function is improved from one release to the next; it may throw SQL errors in situations in which it previously did not. If this happens in a tables constraints; default expressions; partitioning expressions; or virtual columns; the table could not be opened. This prevented both analyzing the problem (using; for example; SHOW CREATE TABLE) and addressing it (such as with an ALTER TABLE ... DROP ... statement).$$$Now; on server upgrade; we scan the data dictionary for tables that use any of the features just mentioned. We then try to open such tables; and if we fail to do so; we alert the user. This patch addresses this. The --check-table-functions server option introduced in this release helps to address this problem by making it possible to specify the servers behavior when encountering an error with such a function. Set this option to WARN in order to log a warning for each table which the server could not open; setting it to ABORT also logs these warnings as WARN; but aborts the server upgrade if any issues were found.$$$ABORT is the default; this enables the user to fix the issue using the older version of the server before upgrading to the new one. WARN flags the issues; but allows the user to continue in interactive mode while addressing the problem. (Bug #36890891)$$$References: See also: Bug #37009318. This issue is a regression of: Bug #98950; Bug #98951; Bug #31031886; Bug #31031888.$$$INFORMATION_SCHEMA Notes$$$Fixed a performance issue in the PROCESSLIST table. (Bug #36778475)$$$Functionality Added or Changed$$$Important Change: For platforms on which OpenSSL libraries are bundled; the linked OpenSSL library for MySQL Server has been updated to version 3.0.16. For more information; see OpenSSL 3.0 Series Release Notes and OpenSSL Security Advisory (11th February 2025). (Bug #36033684)$$$Performance; Replication: The data structure used in tracking binary log transaction dependencies has been changed from Tree to ankerl::unordered_dense::map; which uses approximately 60% less space; and which should thus contribute to better dependency tracking performance. (Bug #37008442; Bug #37529256)$$$InnoDB: To improve debugging; the buf_page_t and buf_block_t structures metadata is now printed to the error log. (Bug #35115629)$$$References: See also: Bug #35115601.$$$Increased the historical 1024-byte limit when printing the current query during signal handling to 1073741824 (1024 * 1024 * 1024). (Bug #37603354)$$$Bugs Fixed$$$InnoDB: Fixed a potential memory leak in several places in the innobase code. (Bug #37403052)$$$InnoDB: Under certain circumstances; M

Changes in MySQL Connector/ODBC 8.0.40 (2024-10-15; General Availability)$$$Bugs Fixed$$$Fixed a potential Out of Bounds (OOB) issue related to escaping large queries. (Bug #36955942)$$$$$$The internal mysql_init() function used for making connections is now thread safe. (Bug #115710; Bug #36894687)$$$$$$With the prefetch connection option set to a non-zero value; large queries could cause the connector to unexpectedly halt. (Bug #113554; Bug #36945554)$$$$$$Fixed the SQLBulkOperations() functions generated WHERE clause; which could potentially cause an application to unexpectedly halt. (Bug #69194; Bug #18641963; Bug #26474373)

Changes in MySQL Connector/ODBC 8.0.37 (2024-04-30; General Availability)$$$The Connector/ODBC 8.0 series contains few changes after Connector/ODBC 8.0.33 and exists as the series to build 32-bit binaries. If you do not require 32-bit binaries then use the latest Connector/ODBC (such as 8.4.0) as it also supports MySQL 8.0 and includes all bug fixes and new features.$$$$$$Security Notes$$$For platforms on which Connector/ODBC utilizes MySQL Servers bundled OpenSSL library (MacOS; Windows; and GenLinux); MySQL Servers linked OpenSSL library was updated to version 3.0.13. Issues fixed in OpenSSL version 3.0.13 are described at https://www.openssl.org/news/cl30.txt. (Bug #36278301)$$$$$$

Changes in MySQL Connector/ODBC 8.0.36 (2024-01-16; General Availability)$$$Bugs Fixed$$$ADODB.Recordset.Open() reported a transaction error when a string type was used with prepared statements. The fix was changing the SQL_MAX_CONCURRENT_ACTIVITIES value from 1 to 0 (unlimited). (Bug #36031548)$$$$$$