MySQL Installer Release Notes

Abstract

This document contains release notes for the changes in each release of MySQL Installer.

For additional MySQL Installer documentation, see Installing MySQL on Microsoft Windows Using MySQL Installer.

Updates to these notes occur as new product features are added, so that everybody can follow the development process. If a recent version is listed here that you cannot find on the download page (http://dev.mysql.com/downloads/), the version has not yet been released.

The documentation included in source and binary distributions may not be fully up to date with respect to release note entries because integration of the documentation occurs at release build time. For the most up-to-date release notes, please refer to the online documentation instead.

For legal information, see the Legal Notices.

For help with using MySQL, please visit either the MySQL Forums or MySQL Mailing Lists, where you can discuss your issues with other MySQL users.

For additional documentation on MySQL products, including translations of the documentation into other languages, and downloadable versions in variety of formats, including HTML and PDF formats, see the MySQL Documentation Library.

Document generated on: 2016-12-23 (revision: 10527)

Preface and Legal Notices

This document contains release notes for the changes in each release of MySQL Installer.

Legal Notices

Copyright © 1997, 2016, Oracle and/or its affiliates. All rights reserved.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

This documentation is NOT distributed under a GPL license. Use of this documentation is subject to the following terms:

You may create a printed copy of this documentation solely for your own personal use. Conversion to other formats is allowed as long as the actual content is not altered or edited in any way. You shall not publish or distribute this documentation in any form or on any media, except if you distribute the documentation in a manner similar to how Oracle disseminates it (that is, electronically for download on a Web site with the software) or on a CD-ROM or similar medium, provided however that the documentation is disseminated together with the software on the same medium. Any other use, such as any dissemination of printed copies or use of this documentation, in whole or in part, in another publication, requires the prior written consent from an authorized representative of Oracle. Oracle and/or its affiliates reserve any and all rights to this documentation not expressly granted above.

Changes in MySQL Installer 1.4.18 (2016-11-04)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Commercial Edition: Enterprise Firewall can be enable or disabled when an installed instance of MySQL server is reconfigured.

An option was added to launch MySQL Shell when the installation of it has finished. The new check box for this option, shown during the Installation Complete step, is selected by default.

Bugs Fixed

Application and connector pre-release versions could not be updated without first removing the older version. (Bug #24928568, Bug #83465)

MySQL servers installed with MySQL Installer returned the mysqldump: [ERROR] unknown option '--no-beep' error message when the mysqldump client utility was invoked. This fix relocates the no-beep option entry within the my.ini file. (Bug #24848000, Bug #83334)

With MySQL 8.0 installed on a system, MySQL Installer was unable to add MySQL 5.7 on the same system to run in parallel. (Bug #24340901)

Commercial Edition: When installing, deleting, and then reinstalling the same version of MySQL server without removing the data path, Enterprise Firewall was not enabled properly and the installation failed. (Bug #22184368)

The default time of the automatic catalog update was changed from 12:00 a.m. to the current time when MySQL Installer was installed or updated. (Bug #20662451)

Changes in MySQL Installer 1.4.17 (2016-08-09)

Bugs Fixed

Running two different installers would register both on the system, instead of having one replace the other. This was noticeable from the Windows Uninstall a Program panel. (Bug #24328360)

MySQL Installer manifest (product catalog) was outdated. (Bug #23627452)

The manifest would sometimes fail to find a newer MySQL Server version. (Bug #23532166, Bug #81728)

Installing MySQL 5.6.x with an installer that bundled MySQL 5.7.x would sometimes emit an unhandled exception. The installation would still properly succeed. (Bug #23526480)

Connector/C versions 6.1.1 through 6.1.3 could not be downloaded and installed from MySQL Installer. (Bug #22954070, Bug #80773)

With the commercial edition, entering incorrect MOS credentials would still move to the next screen, although the downloads would fail. (Bug #22919581)

With the commercial edition, and without an internet connection (offline), selecting a MySQL product from the product cache (not yet downloaded) would emit an "Invalid credentials" error instead of stating that an Internet connection is required to download additional products. (Bug #22917932)

The copyright end date was reported as 2015 instead of 2016. (Bug #22671191)

The Last Updated date displayed under Update Catalog was sometimes incorrect (old). (Bug #22557677, Bug #79921)

The innodb_additional_mem_pool_size option was removed from the default my.ini templates, as it was deprecated in MySQL 5.6 and removed in MySQL 5.7. (Bug #18701859, Bug #72533)

Changes in MySQL Installer 1.4.16 (2016-05-02)

Functionality Added or Changed

The Reconfigure process no longer removes the existing my.ini on the system, when before it overwrote it with all new defaults. Now, the upgrade process updates the existing my.ini file by adding new options (if they exist), leaving all comments, and validating existing settings.

Changes in MySQL Installer 1.4.15 (2016-03-01)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Added a new configuration page for MySQL Server plugins, available when installing MySQL Server versions 5.7.12 and higher.

The installation templates that generate my.ini no longer include an entry for keyring_file_data, as that setting was only required for MySQL Server 5.7.11.

This also fixes the known limitation where the upgrade process did not reconfigure the keyring_file_data option, as my.ini is not overwritten. This was a known limitation with the MySQL Server 5.7.11 keyring plugin, which was enabled by default and required this option.

References: Reverted patches: Bug #22650942.

Bugs Fixed

The MySQL Installer registry location was stored under "HKEY_CURRENT_USER" instead of "HKEY_LOCAL_MACHINE". (Bug #22740141, Bug #80387)

Changes in MySQL Installer 1.4.14 (2016-02-05)

Known limitation: the upgrade process does not reconfigure the keyring_file_data option, because the upgrade process does not regenerate or overwrite the current configuration (my.ini) file. The keyring plugin is new as of MySQL Server 5.7.11, and is enabled by default, but it requires a valid keyring_file_data definition. In MySQL Server 5.7.11, keyring_file_data is set to an invalid (INSTALLDIR) location on Windows. To change it, you can either manually change the setting in my.ini, or click the reconfigure link in the Installer dashboard for your MySQL Server installation to regenerate the my.ini file from scratch. The Installer sets it to "%PROGRAMDATA%/MySQL/MySQL Server 5.7/keyring/keyring".

Bugs Fixed

The installation template was updated to add an entry for the keyring_file_data keyring plugin setting. The Installer sets it to "%PROGRAMDATA%/MySQL/MySQL Server 5.7/keyring/keyring". (Bug #22650942)

Changes in MySQL Installer 1.4.13 (2015-12-02)

Bugs Fixed

The --skip-grant-tables option was removed from the upgrade wizard. (Bug #22277271)

Changes in MySQL Installer 1.4.12 (2015-11-10)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A "passive" parameter was added to the Installer command-line.

The "passive" option won't perform a complete install unless configuration options are used. For example, executing the following will not configure the MySQL server instance, nor will it create the MySQL service:

msiexec /i mysql-installer-community-5.6.27.1.msi /passive
  CONSOLEARGS="install -type=Full -silent"

Passing in configuration options to CONSOLEARGS is recommended, for example:

msiexec /i mysql-installer-community-5.6.27.1.msi /passive
  CONSOLEARGS="install server;5.6.27;x64:*:type=config;openfirewall=true;
    generallog=true;binlog=true;serverid=1;enable_tcpip=true;port=3306;
    rootpasswd=secret:type=user;username=root;password=secret;role=DBManager -silent"

(Bug #19914168, Bug #74622)

Bugs Fixed

The launcher path is now normalized, and extra slashes are removed from the path. (Bug #21685236, Bug #78193)

Several typos and grammatical errors were fixed in the GUI. (Bug #21675183, Bug #21842115, Bug #21503353, Bug #21645361, Bug #78169)

The Accounts and Roles step of the Reconfigure procedure could halt and emit an unhandled exception. This could happen if the initial configuration of MySQL Server was terminated, or otherwise incomplete. (Bug #21648604, Bug #77674)

Upgrading the installer would fail if the user folder (%USERPROFILE%) contained spaces. The full file path is now enclosed in double quotes. (Bug #21574660, Bug #77965)

When the Installer checked for currently installed MySQL products, having a my.ini without a [mysql] section could cause the check to fail and halt the Installer. (Bug #19996084)

MySQL Installer would sometimes fail to check for MySQL Workbench dependencies. (Bug #19676056)

Changes in MySQL Installer 1.4.11 (2015-08-24)

Known limitation: the standard Installer upgrade process will not always upgrade 1.4.10 to 1.4.11. Users that upgraded to 1.4.10 (between 2015-08-19 and 2015-08-23) must manually install 1.4.11. This is recommended. Community edition users can download 1.4.11 from here, and Commercial edition users can download and install the "MYSQL INSTALLER COMMERCIAL 1.4.11 UPDATE PACKAGE (32 BIT)" package from My Oracle Support (MOS). For additional details, see http://bugs.mysql.com/78138.

Bugs Fixed

When MySQL Installer 1.4.10 was checking for existing products installed on the host, an exception was thrown during the Windows firewall detection phase if Windows firewall rules were created without assigned ports after MySQL server was installed. (Bug #21653781, Bug #78138)

Changes in MySQL Installer 1.4.10 (2015-08-19)

Bugs Fixed

The Open firewall port for network access (enabled by default) option would open the firewall ports even when this option was unchecked. Now, if unchecked, the Installer will look for existing MySQL firewall rules and remove them. (Bug #21554742)

Executing MySQL Installer from the command line would not function if the installdir and datadir options contained a colon (":") character, which caused the execution to fail. Paths now work with and require double quotes, such as installdir="C:\MySQL\MySQL Server 5.6", to function. (Bug #21196557, Bug #21381036, Bug #77629)

The upgrade process would suggest Alpha, Beta, and RC releases as upgrades to GA products. (Bug #21147256)

Executing the MySQL Installer MSI with CONSOLEARGS, or in quiet mode, would fail to unpack the product manifest (catalog). (Bug #19919840, Bug #19598843, Bug #74623)

The MySQL Utilities and MySQL Fabric installation path incorrectly contained the point release number (x.y.Z) and also appended an extra major version number (x.y) to the end of the path. (Bug #19658970)

The default max_connection variable was changed from 100 to 151 for MySQL server 5.6 and above. The value is still set to 100 for MySQL server 5.5 and below. (Bug #16664240, Bug #68960)

Changes in MySQL Installer 1.4.9 (2015-08-05)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A new Uploads folder is now created under the datadir directory.

Also, the secure_files_priv option is now added to the generated my.ini configuration file when MySQL server is installed or reconfigured. The secure_files_priv value is equal to the generated Uploads folder. (Bug #15961613)

Bugs Fixed

The Connector/Java product code in the manifest (catalog) was incorrect, which caused the Installer to hang and fail if Connector/Java was one of the selected products. (Bug #21425576)

Having MySQL Installer upgrade itself would sometimes fail and generate an unhandled System.NullReferenceException exception, and also emit "MySQLInstallerConsole has stopped working". (Bug #21212004, Bug #77136)

MySQL Installer would attempt to install Connector/Net 6.9.x when Connector/Net 6.7.x was selected. (Bug #21201970)

The scheduled manifest update would open a new console window when an optional or required upgrade was discovered. The system now waits for the MySQL Installer GUI to be opened before triggering the upgrade process. (Bug #21075124)

The Visual Studio Tools for Office 2010 Runtime requirement was clarified for MySQL for Excel. This requirement is different than Office Developer Tools for Visual Studio, which is not a substitute. (Bug #20003181, Bug #74768)

Changes in MySQL Installer 1.4.8 (2015-05-28)

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

The MySQL Enterprise Firewall installation would report as successful even when it failed. As a workaround, the error was reported in the installation log. (Bug #21085453)

Bugs Fixed

The Installer would sometimes fail to upgrade itself. (Bug #20069174, Bug #74941)

Changes in MySQL Installer 1.4.7 (2015-05-08)

Functionality Added or Changed

MySQL Enterprise Firewall can now be enabled using the commercial version of MySQL Installer.

Changes in MySQL Installer 1.4.6 (2015-04-07)

This release was introduced with MySQL server 5.7.7.

Bugs Fixed

MySQL Installer now accepts the DATADIR argument, and passes it to the MySQL server MSI. The MySQL server MSI writes this value to the DataLocation registry key. (Bug #20517243)

Changes in MySQL Installer 1.4.5 (2015-04-06)

This release was introduced with MySQL server 5.6.24.

Bugs Fixed

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_size directive was defined twice in the generated my.ini MySQL 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.

Changes in MySQL Installer 1.4.4 (2015-02-26)

Bugs Fixed

32-bit binaries of MySQL products were installed on 64-bit systems by default. The installer now defaults to the operating system's build architecture. (Bug #20444148)

The MySQL Installer manifest was missing 64-bit builds of the MySQL Utilities. Therefore, they were neither recognized nor installed. (Bug #19724973, Bug #74190)

It was not possible to simultaneously install Connector/Python 2.0.1 for multiple Python versions, such as Python 2.7, Python 3.3, and Python 3.4. (Bug #19620660)

MySQL Connector/ODBC was missing from the manifest, and this caused the installation to fail when using the web variant of MySQL Installer. A workaround was to manually download and install this connector. (Bug #18551314, Bug #72298)

Changes in MySQL Installer 1.4.3 (2014-11-12)

Bugs Fixed

On a fresh system with Excel 2007, it was not possible to select MySQL for Excel for installation from the custom selection screen. (Bug #19878619)

Products with a build architecture defined as "Any", such as the MySQL server documentation/samples, were not displayed under the 32-bit and 64-bit architecture filters. (Bug #19806591)

The installation process would fail with a system locale other than English (US), due to an unrecognized datetime format. (Bug #19718831, Bug #19897331, Bug #74117)

The Python 2.7 and Python 3.4 versions of Connector/Python 2.0 were not available in the Installer. (Bug #19537904)

The download for MySQL for Visual Studio would fail. A workaround was to use the full installer, as opposed to the web installer. (Bug #19524613, Bug #69789)

Changes in MySQL Installer 1.4.2 (2014-09-26)

A release that includes MySQL server 5.6.21 and 5.7.5, and it is the first public release of the 1.4.x branch. See the 1.4.0 changelog for additional information about this release.

Version 1.4.2 has no changelog entries, or they have not been published because the product version has not been released.

Changes in MySQL Installer 1.4.1 (Not released)

This is another internal release of the 1.4.x branch.

Version 1.4.1 has no changelog entries, or they have not been published because the product version has not been released.

Changes in MySQL Installer 1.4.0 (Not released)

This begins development of the 1.4.x branch, and it includes new features and bug fixes since the previous release. It is an internal release.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

A task can now be scheduled to automatically update the MySQL product catalog. (Bug #18490792, Bug #72171)

Non-GA products are now supported, as these pre-release versions can be installed and updated using the MySQL Installer. The MySQL product listing displays both GA and non-GA releases, and this listing filter is configurable.

Bugs Fixed

Sometimes the upgrade process would modify the installation path of the MySQL server. (Bug #19268803, Bug #67999)

Executing the installer from CLI would install MySQL for Visual Studio even when Visual Studio was not installed on the system. It now checks for this prerequisite. (Bug #19189529)

The Back and Next buttons did not function properly after the installation failed and Try Again was executed. Only Cancel functioned. (Bug #19189513)

Clicking ? on the dashboard now displays the MySQL Installer version number. (Bug #18329551, Bug #19143184, Bug #73166)

The commercial MySQL server 5.5.36 installation package listed a 5.5.35 option, but not one for 5.5.36. (Bug #18080058)

MySQL server 5.7.2 failed to upgrade to MySQL server 5.7.3. (Bug #17809787)

The MySQL Workbench installation now uses the minor version number in the installation path (e.g., 6.2) instead of the point release number (e.g., 6.2.1). (Bug #17759563)

Changes in MySQL Installer 1.3.7 (2014-05-30)

A release that was used with the MySQL Server 5.5.38/5.5.39/5.5.40 and 5.6.19/5.6.20 releases.

Bugs Fixed

The upgrade process required an Internet connection, even with the Skip the check for updates option checked. (Bug #18494397, Bug #72176)

Changes in MySQL Installer 1.3.6 (2014-03-27)

A release that includes MySQL server 5.5.37 and 5.6.17, and later the MySQL server 5.6.18 commercial release.

Bugs Fixed

MySQL for Visual Studio failed to install on a host that only had Visual Studio 2013 installed, as the pre-requisite check only scanned for version 2012 or below. (Bug #18156343, Bug #71474)

MySQL Installer could fail to detect the "VSTO 2010" requirement for MySQL for Excel when Microsoft Office was installed, as Microsoft Office and MySQL for Excel require different versions of the VSTO DLL. Now, the Installer for VSTO is launched when the prerequisite is not installed. (Bug #18078467)

The license conversion process was improved. This process converts MySQL product licenses from Commercial to Community, or Community to Commercial. Also, a product was designated as having a different license if the installed product version was newer than the version known by the Installer. (Bug #17503596, Bug #70408)

Changes in MySQL Installer 1.3.5 (2014-01-31)

A release that includes MySQL server 5.5.36 and 5.6.16.

Bugs Fixed

Sometimes the Installer failed to locate MySQL Server 5.5.35/5.6.15 for download, and under some circumstances, the Installer would crash. (Bug #17375273, Bug #70168)

Changes in MySQL Installer 1.3.4 (2013-12-03)

A release that includes MySQL server 5.5.35 and 5.6.15.

Bugs Fixed

The my.ini template for MySQL Server 5.6/5.7 were updated to use an undecorated value for the innodb_autoextend_increment option, such as 64 instead of the previous 64M. (Bug #17505278, Bug #70412)

Forward slashes were used in the executable path that was defined for the Windows service. These are now back slashes. (Bug #17495554, Bug #70398)

After using MySQL Installer to install MySQL Server and MySQL Workbench, uninstalling MySQL Workbench using MySQL Installer with MySQL Workbench running would force the host to reboot. (Bug #17478598)

Additional architecture validation procedures were added, as MySQL Enterprise Backup binaries do not follow the typical "winx64/win32" file-naming convention. (Bug #17218057)

Changes in MySQL Installer 1.3.3 (2013-09-20)

A release that includes MySQL server 5.5.34 and 5.6.14.

Bugs Fixed

After installation, the anonymous user is removed but the matching schema privileges granted to that user remained. (Bug #17282970)

When performing an upgrade, clicking Add/Modify Product and Features and then choosing MySQL Connectors would generate an unhandled exception. (Bug #17246359)

Changes in MySQL Installer 1.3.2 (2013-07-12)

A release that includes MySQL server 5.5.32 and 5.6.12.

The bundled MySQL Notifier is now 1.1.4 instead of 1.0.3.

Bugs Fixed

My Oracle Support (MOS) passwords with special characters, such as a "+", were not escaped properly which caused MOS authentication to fail when attempting to install commercial products. And failed login attempts are now logged, for debugging purposes. (Bug #16724465)

The upgrade process would replace a custom installation path with the default path. The installation directory is now stored in the registry, and is passed to the Installer during an upgrade. (Bug #16723442, Bug #16783415, Bug #69061, Bug #69060)

The MySQL server 5.7.x installer did not provide a data migration option. (Bug #16663856)

The Installer would remember custom paths from previous installations, which would sometimes interfere with new installations. (Bug #16425173)

MySQL for Excel failed to install on systems with Microsoft Office 2013, as MySQL Installer failed to detect Excel 2013 as a valid prerequisite. (Bug #16293188)

Attempting to execute MySQL Installer while passing in the "/a" parameter with msiexec would cause the installer to fail with an unhandled exception. This is because the installer does not support the administration sequence, and instead only the install sequence ("/i") is supported. The user is now notified of this whenever attempting to pass in "/a". (Bug #16293188)

The Installer would attempt to create a configuration file when the defined data directory did not exist. (Bug #16207721)

If INSTALLLOCATION is passed in while executing the Installer, it will be used as the base directory for all binaries and data files that the Installer installs. And when INSTALLLOCATION is used, uninstalling the Installer will no longer remove files from the ProgramFiles and AppData directories. (Bug #16068507)

The Installer would not detect VSTO, so would fail to install MySQL for Excel on systems that relied upon VSTO. (Bug #15912606)

Changes in MySQL Installer 1.3.1 (2013-07-01)

A release that includes MySQL server 5.5.32 and 5.6.12.

The new Connector/NET 6.7 connector (v6.7.4) branch and MySQL for Visual Studio (v1.0.2) products were added.

Version 1.3.1 has no changelog entries, or they have not been published because the product version has not been released.

Changes in MySQL Installer 1.3.0 (2013-06-03)

A release that includes MySQL server 5.5.32 and 5.6.12.

New products were added to this release: Connector/Python and MySQL Enterprise Backup.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Three new products were added to MySQL Installer: Connector/Python and MySQL Enterprise Backup.

Bugs Fixed

The MySQL 5.7 Command Line Client link, from the Microsoft Windows Start menu, failed to function. It would immediately close. (Bug #16656976)

After selecting all MySQL Products options using the web installer, then pressing the Back button, pressing Next would emit an unhandled exception. (Bug #16534012)

The "Visual Studio Tools for Office 2010 Runtime" prerequisite link was incorrect. (Bug #16521707)

Product requirements were checked after the selection of products for installation, but these requirements are now checked before the product selection process. (Bug #16239108)

It was possible to select both architectures (32-bit and 64-bit) for a single MySQL Server version, which resulted in an error during the installation process. Now only one architecture can be selected per MySQL Server version. (Bug #13978200, Bug #65029)

Changes in MySQL Installer 1.2.0 (2013-04-18)

A release that includes MySQL server 5.5.31 and 5.6.11.

New features include My Oracle Support (MOS) integration, and alternative web installers that download the selected MySQL products instead of bundling them.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

My Oracle Support (MOS) is now integrated into MySQL Installer. You will now receive updates for your commercial MySQL products, and support tickets may now be submitted from within the MySQL Installer.

Web installers were added as an alternative to the full installers. These new installers will download the selected MySQL products instead of bundling them. Versions for both commercial and community editions of MySQL Server 5.5 and 5.6 are available.

Bugs Fixed

A successful return from the netsh command would not be recognized when creating firewall rules. The return code is now checked instead of validating against the string "Ok." (Bug #16338368)

Paths containing special escape characters, such as "\s", "\t", and "\n", would be interpreted and generate invalid paths. For example, "C:\servers\tor\56" would yield "C: ervers or\56". (Bug #16290041)

Some source files were missing license and/or copyright information. (Bug #16283254)

MySQL Installer would remove MySQL Server(s) with different licenses from the one you chose, although the data files were preserved. Instead of removing the old installation, MySQL Installer will now notify you and describe the required steps to continue on with the conversion.

Note that it is not possible to install both commercial and community editions of MySQL Server on a single host. One license type should be chosen and used, otherwise you must first migrate the license. (Bug #16266362)

After creating a user with a wildcard as the host, such as 'user'@'%', a user with the same username could not be created for a different host, such as 'user'@'localhost'. (Bug #16240656)

An installation failed when MySQL Server was not ready to accept connections after the MYSQL56 service was started. An example scenario: if creating the databases required too much time due to slow disks. (Bug #15912543)

The 32-bit and 64-bit versions of the Connector/C++ connector are now defined as mutually exclusive, when before it was possible to select both versions for installation. (Bug #13951621)

Changes in MySQL Installer 1.1.7 (2013-02-15)

A release that includes MySQL Workbench 5.2.47. The MySQL Installer files were incremented from 5.x.x.0 to 5.x.x.1.

Bugs Fixed

On Microsoft Windows, after upgrading a community edition of MySQL Server 5.6.10 to the commercial version, the community edition would remain running. The service is now restarted by MySQL Installer, which now reports the commercial edition as running. (Bug #16339411)

Calls to the netsh.exe command now surround the name argument value with double quotes, because the name argument value might contain a space, such as "Port 3306". (Bug #16317629)

The Network Service user was being translated to a localized string, which could create an invalid Sid. It now uses the built-in "NT AUTHORITY\NetworkService" account. (Bug #16311312)

While adding a MySQL Server, and when using Windows Authentication, the group name would not be validated by MySQL Installer. (Bug #16230325)

On Microsoft Windows 8, updating a community release to a commercial release required you to manually restart the MySQL service after the update. (Bug #16183314)

Changes in MySQL Installer 1.1.6 (2013-02-05)

A release that includes MySQL server 5.5.30 and 5.6.10.

Bugs Fixed

After upgrading from a MySQL Server 5.1 installation, the service for MySQL Server 5.1 was not deleted. (Bug #16238340)

User accounts could not be created using the domain\user layout due to improper escaping. (Bug #16223292)

A new validation routine was added that will report an error while attempting to create a user that already exists. Before MySQL Installer would silently fail. (Bug #16204038)

Passing in the "--product=*" option to the MySQL Installer Console would not function when used to remove products with the "--action=remove" option. (Bug #15860256)

A Migrate 5.5 data to 5.6 Server with Workbench option was added. If MySQL Server 5.5 data is present, and MySQL Server 5.6 is being installed, then it will be selected by default. If it and the Launch MySQL Workbench option are both selected, then completing the installation will load MySQL Workbench with the --migrate55to56 directive. This initiates a simplified database migration wizard in MySQL Workbench. (Bug #14834852)

mysql_upgrade.exe is now automatically executed after performing a MySQL Server upgrade. (Bug #14834832)

Certain characters were not allowed for the user passwords, such as the string "',.pyf". (Bug #13702313)

Changes in MySQL Installer 1.1.5 (2012-09-30)

A release that includes MySQL server 5.5.28 and 5.6.6 m9.

Bugs Fixed

The MySQLInstallerConsole command would sometimes return 0 if the command failed. It will now only return 0 on success. (Bug #14698363)

Setting up the Windows Service to use a Custom User will no longer proceed to the next step until after the custom user has rights to log on as a service. (Bug #14666804)

The Installer would not upgrade the community version of MySQL Server 5.5 to a commercial version of MySQL Server 5.6. (Bug #14395130)

The copyright year would display 2011 instead of 2012. (Bug #14005334, Bug #13963475)

The MySQLInstallerConsole --help content was incomplete, and the Installer text contained typographical errors. (Bug #13963477, Bug #14702055)

The Remove Server Data option was only available after the MySQL Server was removed. It is now available after any MySQL product is removed. (Bug #13856677)

The MySQL 5.x Command Line Client shortcut did not function. (Bug #13331360)

The no-beep option is now enabled by default in the bundled my.ini configuration file. (Bug #11745551, Bug #17088)

Changes in MySQL Installer 1.1.4 (2012-08-08)

A release that includes MySQL server 5.5.27 and 5.6.6 m9.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

While creating a user, the Installer will now warn the user if a username exceeds 16 characters in length.

Bumped the bundled MySQL Server versions to 5.5.27 and 5.6.6 m9.

Bugs Fixed

MySQL Installer failed to upgrade previous installations of MySQL Server. (Bug #14520795)

Pressing Execute on the Requirements page would attempt to download and install Microsoft Excel 2007 if the MySQL for Excel plugin was checked, and if Microsoft Excel was not already installed. The requirement is now removed after pressing Execute, and the plugin will not installed. (Bug #14400072)

The Resources, Webinars link was broken. (Bug #14388586)

MySQL Server installations that were installed from the older MySQL MSI would not be detected by MySQL Installer. (Bug #14277765)

Documentation and example packages failed to install with the MySQL Server 5.1 installer. (Bug #13702317)

The Check for Updates option would sometimes fail to function. (Bug #13627586)

The Windows Installer now adds full permissions for the user executing the Installer to files that are created by the Installer, which includes my.ini. Before, only those with administrative rights would have these privileges. (Bug #11753720)

Selecting Show Advanced Options adds a fourth installation step, but the counter would continue to be labeled as "x of 3" steps. It would jump from "3 of 3" to "4 of 4" steps. (Bug #65067, Bug #13992155)

MySQL 5.5 failed to install properly if MySQL 5.1 was already installed. It would report that the datadir of a previously installed MySQL 5.1 installation conflicted with the MySQL 5.5 datadir, and would require the user to define an alternative directory path. (Bug #62440, Bug #13007042)

Changes in MySQL Installer 1.1.0 (2012-07-25)

Developmental release of the MySQL Installer.

Functionality Added or Changed

Bugs Fixed

Functionality Added or Changed

Added the ability to create user accounts.

Added the ability to run MySQL as a new local user.

Added an advanced configure option, which allows the definition of multiple log files.

Added the new MySQL for Excel for Microsoft Windows product, which is now installed by MySQL Installer

Added the new MySQL Notifier for Microsoft Windows product, which is now installed by MySQL Installer

Bugs Fixed

MySQL Installer failed to upgrade MySQL Server if the previous installation of MySQL Server was not installed by MySQL Installer, and if MySQL Installer was auto-launched during its installation.

A workaround is to close the initial instance of MySQL Installer, and then launch MySQL Installer from the Start Menu. (Bug #14277765)

Fixed several typos in the MySQL Installer help dialogue, including grammar and URL updates. (Bug #64095, Bug #13639253)

Connector/Net was added to the MySQL Installer. (Bug #60861, Bug #12401368)

The MySQL Server 5.5.25a release is displayed as version 5.5.26. This is due to a MSI limitation.