Changes in MySQL Installer 1.6.3 (2022-05-26)

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• MySQL Installer now enables granting access control on named-pipe connections during the server configuration process. If selected, access control can be set to one of the following levels to permit communication between client software and the server using a named pipe:

  • Minimum access to all users (default)

  • Full access to members of a local group

  • Full access to all users

  A Windows administrator must create and manage the local group, if that level is selected, and group members must adhere to the requirements established by Windows. For additional information about this new configuration option, see Type and Networking. (Bug #32259975)

Bugs Fixed

• Updated versions of the sakila and world databases now use the correct encoding (UTF8) when running the script that creates each database. Previously, an ASCII encoding produced issues when displaying characters. (Bug #34074353)

• Even though a successful authentication to MySQL Oracle Support (MOS) was reported, incomplete authentication could cause a subsequent upgrade operation to fail if the catalog update approach was used and the prompt to upgrade Commercial MySQL Installer was accepted. (Bug #33917044)

• During the first execution of MySQL Installer, a product catalog merge is performed. The merge consists of incorporating the packages found in the local products.xml file into the recently downloaded products.xml file. The expected merge operation should add the merged packages to the beginning of the packages list, but it added them to the end. The incorrect merge prevented the CLI from ordering the available packages for installation properly. (Bug #33911857)

• An onscreen message indicated that an installation operation was to be performed, but the actual operation downloaded the selected packages in preparation for the installation. This fix changes the text to match the action. (Bug #32092220)

• An invalid path to the binary log, if provided as a logging option during the server configuration process, prevented the server from starting. Improved validation now confirms the path to the log. (Bug #30901084)

• Samples & Examples and Documentation products were removed from the Client-Only setup type description. The erroneous description was shown in the Setup Type page when no other MySQL products were installed. (Bug #30883963)

• An invalid installation directory path and data directory path (for server only) could be specified during a custom installation. (Bug #30509895)

• MySQL Installer was unable to apply a server configuration that supported named-pipe connections only, causing the installation to fail because a connection to the server could not be established. (Bug #30335945)

• After installing a server instance that was configured to use named-pipe connections only, the Windows shortcut to the MySQL client was unable to establish a connection to the server when valid credentials were provided. Now, the shortcut's configurations is updated properly to run the server with support for named-pipe connections. (Bug #22270306)

• The templates used to generate the my.ini server-options file now report the accurate default location of the installed my.ini file (under %ProgramData%), rather than misreporting %ProgramFiles% as the file's default location. (Bug #85469, Bug #25730095)