Bug #64928 Changing the default storage engine later has no effect

• Submitted: 10 Apr 2012 13:04
• Modified: 31 Jan 2013 7:26
• Reporter: [ name withheld ]
• Status: Closed
• Category: MySQL Workbench: Modeling
• Severity: S2 (Serious)
• Version: 5.2.38
• OS: Windows
• CPU Architecture: Any

[10 Apr 2012 13:04] [ name withheld ]

Description:
I use MySQL Workbench 5.2.38. and I have made an EER Diagram. But on export I got surprised with InnoDB as defined storage engine. Altering the table afterwards is not an option because I do not have an InnoDB engine.

ERROR 1286 (42000): Unknown storage engine 'InnoDB'

So, I have changed the Default Engine via Edit-> Preferences -> Model: MySQL to MyISAM but on export there is still InnoDB in use?!

I am completely unable to change the storage engine.

How to repeat:
1 create a new model
2 create a new EER diagram
3 create a new table
4 export ddl -> look for storage engine
5 goto edit-> preferences -> Model: MySQL and change ste storage engine
6 export ddl -> look for storage engine

[10 Apr 2012 13:44] Valeriy Kravchuk

I think it is intended and expected that default engine setting applies to a table when it is created/added to the model. If you want to change engine later you should do this explicitly for every table used.

At the same time, it would be nice to have some way to change engine for all tables in the model (or for all tables where it was not set explicitly). So, I think this is a valid feature request.

[12 Apr 2012 11:51] [ name withheld ]

How can you cahange te engine explicitly? I am not able to find an option where you can do this. And the Held leads me to Workbench Preferences where I can not find the suggested "MySQL" Tab.

[8 May 2012 21:18] Miran Miksic

You can change the engine of a table in a EER diagramm by going into the "Edit table" tab and then clicking on the symbol on the right which looks like a '>>' directing towards bottom. This will show you 3 additional fields including the db engine.

[31 Jan 2013 7:26] Philip Olson

Fixed as of the upcoming MySQL Workbench 5.2.46, and here's the changelog entry:

The "Model: MySQL", "Default Storage Engine" preference would not take
effect until after MySQL Workbench was restarted.

Thank you for the bug report.