Bug #6574 Start Up Variables, Inno-DB tickbox activated on new start
Submitted: 11 Nov 2004 11:56 Modified: 3 Feb 2006 13:27
Reporter: Mike Bailey Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Administrator Severity:S3 (Non-critical)
Version:1.0.14 Windows msi OS:Windows (WinXP)
Assigned to: MySQL Verification Team CPU Architecture:Any

[11 Nov 2004 11:56] Mike Bailey
Description:
Refers to Startup Variables, Inno-DB Parameter Tab:
Each time the MA is restarted the Inno-DB activate tick box is re-activated, despite the configuration of MySQL with only MyISAM and no Inno-DB and the tick-box being unticked and "changes applied" on previous call to MA.  

How to repeat:
During installation and configuration install only MyISAM table support.
Start MA, select Startup Variables, Inno-DB Tab. 
The Inno-DB activate tick box is activated
Click this away and click 'Apply Changes'.
Close MA.
Restart MA and navigate to Startup Variables, Inno-DB Tab.
The tick box is again activated.

Suggested fix:
Suspect that this is not being stored (or reread) correctly in the my.ini file.
[12 Nov 2004 17:07] Charles Canato
I also have this bug. In fact, this may lead to other parameters as well, as it seems that some existing startup variables are not correctly interpreted/recognized by MA.

The "skip-innodb", as told above, is one of them. When you "Apply Changes" at MA, if you take a look at the file, it prefixes the parameter with a "#(unknown)" (sorry, erased it, don't remember it exactly, but it's something like this) string. When you activate it, it puts exactly the same parameter back to MY.INI, just for it to get again disabled in the next Startup Variables change in MA.

This ALSO happens to the "enable-named-pipe" parameter, which gets prefixed the same way. Maybe this one is more understandable, since there's no way to enable or disable it in Startup Variables module.
[4 Feb 2006 0:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".