Changes in MySQL 5.7.44 (2023-10-25; General Availability)$$$Important$$$MySQL 5.7.44 is the final release of the MySQL 5.7 series.$$$$$$MySQL 5.7 users are encouraged to upgrade to the latest MySQL 8.0 or MySQL Innovation release.$$$$$$SQL Function and Operator Notes$$$$$$Packaging Notes$$$$$$Functionality Added or Changed$$$$$$Bugs Fixed$$$$$$SQL Function and Operator Notes$$$The STR_TO_DATE() function did not perform complete range checking on the string to be converted; so that it was possible to pass to it a string which would yield an invalid date; such as 2021-11-31. (Bug #108782; Bug #34704094)$$$$$$Packaging Notes$$$On Windows; the MSI package definition files were updated to work with the Windows Installer XML (WiX) toolset version 4. Note that they can no longer be used with previous versions of the toolset. (Bug #35613791)$$$$$$The bundled libedit library was upgraded to version 20221030-3.1. (Bug #35489173)$$$$$$Functionality Added or Changed$$$Important Change: The linked OpenSSL library for MySQL Server has been updated to version 3.0.10. Issues fixed in OpenSSL version 3.0.10 are described at https://www.openssl.org/news/cl30.txt. (Bug #35702863; Bug #35732474)$$$$$$Bugs Fixed$$$InnoDB: Fixed processing of single character tokens by a FTS parser plugin.$$$$$$Our thanks to Shaohua Wang for the contribution. (Bug #35432973)$$$$$$InnoDB: The last detected deadlock section of the engine status log was only showing 1024 characters for the combined thread and query information. Fixing by removing the printed query string limit. (Bug #80927; Bug #23036096)$$$$$$Some complex queries using multiple common table expressions were not always handled correctly. (Bug #34900334)$$$$$$References: This issue is a regression of: Bug #34377854.$$$$$$

Changes in MySQL 5.7.43 (2023-07-18; General Availability)$$$Compilation Notes$$$$$$Functionality Added or Changed$$$$$$Bugs Fixed$$$$$$Compilation Notes$$$Improved Clang 15 usage; although its not officially supported in v5.7. (Bug #34638573; Bug #35278042)$$$$$$Functionality Added or Changed$$$Important Change: The linked OpenSSL library for MySQL Server has been upgraded from OpenSSL 1.1.1 to OpenSSL 3.0. The exact version is now 3.0.9. More information on changes from 1.1.1 to 3.0 can be found at https://www.openssl.org/docs/man3.0/man7/migration_guide.html. (Bug #35475140; WL #15614)$$$$$$The linked curl library for MySQL Server (Enterprise Edition) has been updated to version 8.1.1. (Bug #35329529)$$$$$$Bugs Fixed$$$Group Replication: After one machine halted and restarted in a three-node MySQL InnoDB Cluster; one node failed to start; after restarting all nodes; the cluster shut down unexpectedly.$$$$$$Our thanks to Zetang Zeng for the contribution. (Bug #34976442)$$$$$$Fortified parsing of the network packet data sent by the server to the client. (Bug #35374491)$$$$$$Some floating-point literals were not always handled correctly. (Bug #32824429)$$$$$$Executing a query with an implicit aggregation should return exactly one row; unless the query has a HAVING clause that filters out the row; but a query with a HAVING clause which evaluated to FALSE sometimes ignored this; and returned a row regardless. (Bug #14272020)$$$$$$During optimization; range-select tree creation uses logic which differs based on the left-hand side of the IN() predicate. For a field item; each value on the right-hand side is added to an OR tree to create the necessary expression. In the case of a row item comparison (example: WHERE (a;b) IN ((n1;m1); (n2; m2); ...)); an expression in disjunctive normal form (DNF) is needed. A DNF expression is created by adding an AND tree with column values to an OR tree for each set of RHS values; but instead the OR tree was added to the AND tree causing the tree merge to require exponential time due to O(n2) runtime complexity. (Bug #108963; Bug #34758905)