Bug #45201 Windows configuration wizard allows changes to Innodb settings on reconfigure
Submitted: 29 May 2009 22:52 Modified: 17 Jun 2009 21:51
Reporter: Patrick Crews Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Server: Config Wizard Severity:S3 (Non-critical)
Version:5.0+ OS:Microsoft Windows
Assigned to: Iggy Galarza CPU Architecture:Any
Tags: .msi, configuration, Configuration Wizard, Innodb settings, windows
Triage: Triaged: D3 (Medium)

[29 May 2009 22:52] Patrick Crews
Description:
The Windows configuration wizard allows for changes to the Innodb tablespace settings during a re-configure, but I don't think this should be allowed.

When upgrading a version of the server (say 5.1.31 -> 5.1.35 <as tested>), during the configuration of the upgraded server, the Innodb tablespace settings are greyed out and the user must manually select Modify to change them.

This results in a warning being presented that the user must manually move / copy existing files from the current location to the new one.

It seems that such a thing should also occur during a reconfigure of the server - the user should be warned that a change in tablespace settings require manual file movement to ensure continued operation of Innodb tables.

How to repeat:
To observer update behavior:
1) Install a version of the server and configure it.
2) Install an upgrade of the same server version (5.1.31 -> 5.1.35)
3) Observer during the configuration of the new server that the Innodb settings are greyed out and the user must use a 'Modify' button to alter them.  Choosing 'Modify' will result in the presentation of a warning prompt.

To observe re-configure behavior:
1)  Install a version of the server and configure it.
2)  Re-configure it and observe that the Innodb settings are able to be changed without presenting a warning, etc.

Suggested fix:
It seems that any change in Innodb tablespace settings should result in a warning to the user so that they can either choose to abort the change or make the manual changes needed to ensure that Innodb tables continue to work with the changes.