MySQL Bugs: #49750: MySQL 5.5 installation ignores existing MySQL 5.4 data

Bug #49750	MySQL 5.5 installation ignores existing MySQL 5.4 data
Submitted:	16 Dec 2009 22:00	Modified:	31 Mar 2014 10:21
Reporter:	Peter Brawley (Basic Quality Contributor)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Config Wizard	Severity:	S3 (Non-critical)
Version:	5.5	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
The convention offered by MySQLInstanceConfig.Exe of placing MySQL data in the %programfiles% folder hierarchy is stupid enough. If a user wishes to avoid having to dump 5.4 data and manually restore it to the 5.5 installation, she cannot do so, since MySQLInstanceConfig.Exe does not include 5.4 data folders in selectable options. Not user-friendly.

How to repeat:
As above.

Suggested fix:
This looks like another loose end from the switch in "release models". The user has every reason to think of 5.5 as a minor upgrade from 5.4, but MySQLInstanceConfig.Exe treats it as an entirely separate puppy. Not a good way to win user loyalty.

Thank you for the report.

Verified as descried. Strictly say this is not a bug, but feature request, because 5.5 is different from 5.4, but would be good to have a way to specify datadir in Windows Configuration Wizard.

> Strictly say this is not a bug, but feature request, because 5.5 is different from 5.4

Sorry, that's a bureaucratic evasion of the problem.

Posted by developer:
 
Thank you for the bug report. We are closing this report now since the original config wizard is no longer the focus of Windows deployment efforts. For recent MySQL Server versions, the config wizard is also no longer available, and the MySQL Installer for Windows is the recommended way to install MySQL Server on Windows.

Closing as per comment above.