Bug #49010 Make default storage engine a free-text field (in WBA)
Submitted: 23 Nov 2009 23:49 Modified: 14 Dec 2009 17:03
Reporter: Todd Farmer (OCA) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2 r4753 OS:Any
Assigned to: Maksym Yehorov CPU Architecture:Any

[23 Nov 2009 23:49] Todd Farmer
Description:
One of the flagship features of MySQL 5.1 is the support for pluggable storage engines.  That makes the constraints imposed in WB around the default storage engine (when manipulating the general configuration properties) quite incomplete (especially since not all MySQL-produced storage engines are represented):

* Falcon (really!)
* InnoDB
* Heap
* MyIsam (capitalized that way)
* BDB (!)

The following MySQL-produced storage-engines are missing:

* NDB (and equivalent NDBCluster)
* ARCHIVE
* MERGE
* FEDERATED
* BLACKHOLE
* CSV
* IBMDB2I
* EXAMPLE
* MEMORY (synonym for Heap)

And that's really just the list of MySQL-produced storage engines.

It's silly for this field to be so constrained.

How to repeat:
Try to select all of the mentioned storage engines from the drop down for default storage engine.

Suggested fix:
Make a plain text field, perhaps with type-assist suggestions for MySQL-produced storage engines.
[24 Nov 2009 20:03] Alfredo Kojima
I see more than 20 storage engines in the pulldown list, including the ones you mention and no incorrectly capitalized MyISAM. Where and in what OS did you see such truncated list?
[24 Nov 2009 20:31] Alfredo Kojima
Found the problem, it's in WBA, configuration file editor. The list of storage
engines should be dynamically queried from grt.root.wb.options.options["@db.mysql.Table:tableEngine/Items"]
[3 Dec 2009 18:29] Maksym Yehorov
Fixed
[14 Dec 2009 14:27] Johannes Taxacher
this has been changed to feature the list of engines stored in Workbench backend.
will be included in 5.2.11
[14 Dec 2009 17:03] Tony Bedford
An entry has been added to the 5.2.11 changelog:

In the General tab of the configuration editor in the Admin screen, the option Default table type provided an incomplete, and incorrectly capitalized, list of storage engines/table types.