MySQL Bugs: #27781: Installer overwrites configuration file

Bug #27781	Installer overwrites configuration file
Submitted:	12 Apr 2007 10:47	Modified:	7 Feb 2008 22:12
Reporter:	Sveta Smirnova	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Server: Installing	Severity:	S4 (Feature request)
Version:	5.0.37	OS:	Windows (Vista, should be all)
Assigned to:	Iggy Galarza	CPU Architecture:	Any

Description:
Configuration wizard overwrites existing configuration file including not mentioned in dialog settings

How to repeat:
1. Install MySQL server with default settings.
2. Change configuration file.
3. Upgrade MySQL server.
4. Run configuration wizard, change some settings.

Suggested fix:
Not mentioned in the wizard settings (as shared_memory etc.) should not be changed.

This is not a bug but rather an enhancement request for these reasons:

#1. The current configuration file is not overwritten, instead it's copied to a backup file in the same directory.  The backup file name will use this format:
"my [yyyy-mm-dd hhhh].ini.bak" on Windows.

#2. The option to reconfigure an instance currently has this description:
"Select this option to create a new configuration for the instance. This will replace the current configuration and restart the service if it is currently running." so, MySQLInstanceConfig.exe does exactly what it tells you it will, namely "replaces existing configuration"

This enhancement should not be implemented because it would detract from the usefulness of the Config Wizard. Currently the advanced user has the ability to diff her new and old option files to quickly identify and/or patch her custom configurations into the new option file.  This change would eliminate that possibility and force the user to keep all custom options.  At best, the Config Wizard could implement a limited version of the functionality provided by diff/patch, which would be of minimal usefulness to the end user.  For these reasons, I've marked this enhancement as "Won't Fix".