Bug #35293 Add a setting to the schema for a default engine
Submitted: 14 Mar 2008 14:29 Modified: 3 Aug 2009 17:54
Reporter: Mike Lischke Email Updates:
Status: Won't fix Impact on me:
Category:MySQL Workbench Severity:S4 (Feature request)
Version:5.0.14a OS:Any
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: CHECKED, engine, schema, settings

[14 Mar 2008 14:29] Mike Lischke
It would be very helpful to have a per-schema setting for a default engine, which is then used for any newly created table. 

How to repeat:

Suggested fix:
Add an option for the default engine to the schema settings and follow these rules:

1) If no engine is set for a table or the containing schema then use the default engine of the server.
2) If there is an engine given in the schema but not in the table then use the one given for the schema. Fill it in the edit control already while creating the table.
3) If an engine for the table is given use that regardless of server or schema default engine.

For existing tables when the default is changed: don't change the tables. The default engine is only applied when creating a table. Changing the engine for a group of existing tables can be the task for a plugin.
[3 Aug 2009 17:54] Alfredo Kojima
A per-model setting for default engine makes more sense than per-schema, which is already implemented.
I'll close this as Won't Fix.