Documentation Home
MySQL Installer Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 165.0Kb
PDF (A4) - 164.9Kb
HTML Download (TGZ) - 44.6Kb
HTML Download (Zip) - 98.5Kb


MySQL Installer Release Notes  /  Changes in MySQL Installer 1.4.33 (2020-03-04)

Changes in MySQL Installer 1.4.33 (2020-03-04)

Known limitation: There is an issue for MySQL 8.0.16 and higher that prevents the server from starting when the data directory from an earlier server version is reused for a new server installation. MySQL Server automatically initiates an upgrade when an existing data directory from an earlier server installation is reused and MySQL Installer does not process the upgrade as expected.

The workaround is to use the Upgrade operation in MySQL Installer, instead of removing the earlier server installation and then installing a fresh server instance that reuses the previous data directory. Alternatively, install a new server instance with the same version number as the data directory to be reused, then upgrade the server afterwards.

Functionality Added or Changed

  • MySQL Installer no longer discovers the following MySQL products and product series. All actions to these products, if they are currently installed, must be performed manually.

    Products removed from the manifest:

    • MySQL Utilities

    • MySQL Fabric

    • MySQL Connector/C

    Product series removed from the manifest:

    • MySQL Server 5.1, 5.5

    • Samples 5.1, 5.5

    • Documentation 5.1, 5.5

    • MySQL Workbench 5.2, 6.0, 6.1, 6.2, 6.3

    • MySQL Notifier 1.0

    • MySQL for Excel 1.0, 1.1, 1.2

    • MySQL Enterprise Backup 3.8, 3.9, 3.10, 3.11, 4.0

    • MySQL for Visual Studio 1.0, 1.1

    • MySQL Connector/ODBC 5.1, 5.2

    • MySQL Connector/J 6.0

    • MySQL Connector/NET 6.4, 6.5, 6.6, 6.7, 6.8, 6.9, 7.0

    • MySQL Connector/Python 1.0, 1.1, 1.2, 2.0, 2.1, 2.2, and 8.0 (for Python versions 2.7, 3.5, 3.6, and 3.7 only)

    (Bug #29649739, Bug #30544452)

Bugs Fixed

  • The connection test performed after reconfiguring an existing InnoDB cluster to be a sandbox InnoDB cluster reported that the connection was unsuccessful, because an alternative port was used for the test. This fix ensures that the user-defined connection details are always used when testing a reconfigured cluster connection. (Bug #30830259)

  • Previously, MySQL Installer included plugin-load entries in the my.ini server configuration file to install MySQL Enterprise Firewall. The file entries introduced errors in the server log during an upgrade when the loading operation was attempted. This fix removes the plugin-load entries from the file and now executes the SQL script supplied by the MySQL Server to create all of the supporting objects required to install the plugin. (Bug #30725039)

  • A success icon was shown incorrectly after an attempt to remove a product failed and the operation included no suboperations. (Bug #30669574)

  • Ineffective validation determined that all products set with relatedVersion=8.0 in the products manifest were installed already when Connector/Python 8.0.19 was selected for installation. The error disabled the selection arrows for related items, such as MySQL Documentation 8.0.19 or Samples and Examples 8.0.19, during the Select Products and Features step. (Bug #30556167)

  • A port number other than the default 3306 added an error to the log for a MySQL server instance that was installed using MySQLInstallerConsole.exe while another server instance with the default port was installed already. Now, the default port value can be overridden as expected and all ports in use already are identified. (Bug #30428696, Bug #97252)

  • An issue with Connector/Python blocked the installation of other MySQL connectors and clients. (Bug #30377477)

    References: See also: Bug #30556167.

  • An exception was returned unexpectedly when the MySQLInstallerConsole INSTALL command was used. (Bug #30298310)