MySQL Installer Guide
This release was introduced with MySQL server 5.6.24.
When the product catalog (manifest) update wizard discovered a new version of MySQL Installer, the upgrade wizard would not close the current MySQL Installer instance, and the upgrade process would fail. (Bug #20781322)
Sometimes the manifest update operation would fail, and the product catalog would not update. MySQL Installer now adds an empty product catalog update file on the system. (Bug #20765093)
The MySQL Installer upgrade process would change the default MySQL server version. (Bug #20765084)
For new installations, the web version of MySQL Installer now automatically updates the product catalog (manifest) before installing products on the system. If MySQL Installer was already installed on the system, then the current product cache is used. (Bug #20692839, Bug #76241)
-
A new installation would sometimes fail while performing a "Developer Default" or "Full" type of installation, and instead it would report the following error: "Unable to determine the products that correspond with that setup type."
Workaround: perform a "Custom" type of installation. (Bug #20425194, Bug #75511)
The
sort_buffer_sizedirective was defined twice in the generatedmy.iniMySQL configuration file. (Bug #19769823)The most recent version of MySQL Notifier could not be downloaded and installed. (Bug #19686961, Bug #74070)
MySQL Workbench would fail to install if the system did not have Microsoft Visual C++ 2013 runtime installed. (Bug #19669733)
MySQL Installer failed to find verify the Connector/Python prerequisites. (Bug #19606868)
-
The web variant of MySQL Installer (Installer only, without the bundled MySQL products) is no longer available for the commercial edition, as the My Oracle Support (MOS) account requirement hindered its usefulness. The full version of MySQL Installer remains available for both commercial and community editions of MySQL.
This change affects the MySQL 5.5.43 and 5.6.24 releases, and above.