MySQL Bugs: #55927: Workbench has Incorrect Default Storage Engines that can be written to my.cnf

Bug #55927	Workbench has Incorrect Default Storage Engines that can be written to my.cnf
Submitted:	11 Aug 2010 21:17	Modified:	29 May 2013 18:53
Reporter:	Chris Calender	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.26	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any
Tags:	default storage engine, kfdb, pbxt, workbench

Description:
Workbench has incorrect options available for the "Default Storage Engine" setting.  If you attempt to set it to one of these incorrect options, it will write it out to your my.cnf or my.ini file.  However, the next time you attempt to restart mysqld, it could fail to start.

The "default storage engine" shows "PBXT" and "KFDB" -> neither of which are in 5.0 nor 5.1 (at least not by default).

Also, it shows "Example" engine, but it is not enabled by default in 5.0 or 5.1.  So if the engine could not be used, then it should not be available to select in Workbench.

How to repeat:
1. Open Workbench.
2. Connect to mysqld under "Server Administration".
3. Navigate to "General" tab.
4. Select "PBXT" as the Default Storage Engine, and "apply" it.
5. Restart your mysqld.

Suggested fix:
Only allow supported Storage Engines to appear as options for the "Default Storage Engine" value.

The default storage engine option in the config file settings is a line edit control in recent MySQL Workbench versions, so no options are presented.