MySQL Installer Guide
All sandbox InnoDB Cluster configuration entries now are stored in the
installer_config.xmlfile, which is located in the same folder as themy.inifile. Previously used.inifile templates are no longer valid for starting servers in a sandbox InnoDB Cluster test setup. (Bug #27222797)By design, an existing sandbox InnoDB Cluster test setup will be removed and recreated during the configuration step of a MySQL server upgrade to ensure that the test setup operates with the new server version properly. Alternatively, if the standard configuration procedure is bypassed, each instance of the sandbox InnoDB Cluster must be recreated or upgraded manually (see Upgrading MySQL). (Bug #26317121)
The program links created by MySQL Installer to open the MySQL command-line clients now use the configuration file of the seed instance created during the sandbox InnoDB Cluster configuration. (Bug #26316808)
Added password verification to the sandbox InnoDB Cluster test setup. Also added a visual alert to report the password strength, which makes the new password check consistent with the way a
rootpassword is checked during the standalone server configuration. (Bug #25925661)The procedure used by MySQL Installer to override the installation location defined within a standalone MSI file was enhance to ensure that user-defined installation paths can be set correctly. This fix resolves the specific case in which the MySQL Shell MSI file provided an unexpected property to set the default install location. (Bug #25872227)
Enabled TLS 1.2 protocol for all downloads made by the MySQL Installer for Windows. (Bug #25819758)
Reconfiguring MySQL server to use classic MySQL replication instead of running a sandbox InnoDB Cluster test setup no longer requires a password. In previous releases, a password enabled MySQL Installer to stop the sandbox cluster gracefully before attempting to perform a classic configuration and then to start the sandbox cluster after the classic configuration finishes. The requirement to stop and start the sandbox cluster first is now unnecessary. (Bug #25814476, Bug #25925633, Bug #27090803, Bug #25884394)
Incorrect detection rules for the Visual Studio Tools for Office prevented the installation of MySQL for Excel. This fix changes the rules to check a Windows registry key in the
Registry32view instead of in the default view. (Bug #27170639)MySQL for Visual Studio (32-bit) detection rules failed to locate prerequisite software even when it was installed. (Bug #26943730, Bug #88034)
An older VC++ 64-bit runtime also required the corresponding 32-bit version to the satisfy prerequisite requirements. This fix updates the links to retrieve the latest Microsoft software. (Bug #26926298, Bug #87962)
MySQL Installer processed catalog updates incorrectly causing error messages. Now when new products are found during a catalog update, only the required information is processed. (Bug #26423059, Bug #86999, Bug #26427818, Bug #87009)
Improvements to the description of Samples and Examples now clearly identify which version applies to standalone server configurations and which to sandbox InnoDB Cluster test configurations. In addition, it is now possible to install the database samples on multiple instances and to filter out read-only MySQL server instances that may be slaves in an InnoDB Cluster for which data cannot be created. (Bug #26037587)
A misdirected link to the MySQL Shell release notes was corrected. (Bug #25962539)
User-defined installation paths were overwritten by the default value every time the configuration step was launched. With this fix, the default path value is set one time only. (Bug #25885341)
The Windows authentication plugin was not inserted into the configuration file when Windows-authenticated users were added during the server configuration. (Bug #25802636)
The configuration log included messages from when Windows Firewall ports were opened, but the messages indicated incorrect port numbers. (Bug #25440217)
When configuring sample databases for MySQL 5.5, the configuration step succeeded but with errors. This fix adjusts the
MAX_ALLOWED_PACKETvalue in the configuration file of MySQL 5.5 installations to match the value set for MySQL 5.6 and newer server versions. (Bug #25185242)When the catalog was scheduled to update automatically, a task window for the update operation was displayed at the same time each day. This fix eliminates the visual alert. (Bug #23735774, Bug #82087, Bug #25677507)
Some of the interactive configuration instructions were updated to improve usability. (Bug #23061485, Bug #80971)
The default folder name created for MySQL Connector/ODBC 5.3.x was changed from
Connector.ODBC 5.3toConnector ODBC 5.3to match the default folder created by the standalone MSI file. (Bug #22914752)When a blank or empty user name with a valid password was given as credentials for creating a new MySQL user account in the Accounts and Roles screen, the empty user name was accepted but the operation produced an error without providing a way to replace the user name. This fix validates that a user name is neither blank nor empty before attempting to add the user account. (Bug #22575954)
When configuring a server after an upgrade, the option to skip the upgrade check and process (not recommended) appeared to preform the task if the check box was first selected and then deselected. In contrast to the success indicator (a green check mark), the task was not performed. (Bug #21055769)
Passwords that contained special characters such as semicolons (;) were improperly formatted before the password was sent to the server, resulting in an error during the server configuration step. (Bug #20102532, Bug #75008)
Entries in the Change History log when viewed as text exceeded the space provided with no option to scroll. (Bug #19914442)