MySQL Bugs: #60258: default engine not applied to new tables with engine field blank

Bug #60258	default engine not applied to new tables with engine field blank
Submitted:	25 Feb 2011 20:54	Modified:	29 Jun 2011 16:03
Reporter:	Phellipe Kelbert	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.31	OS:	Linux (Ubuntu 10.04)
Assigned to:		CPU Architecture:	Any
Tags:	engine preferences

Description:
i have engine "innodb" configured as default engine on "mysql" tab at "preferences" window.

when i create new tables by leaving engine field blank, the tables are not created with "innodb" engine but with "myisam" instead.

How to repeat:
 - under "edit" menu, click "preferences" and then "mysql" tab;
 - set "innodb" as default storage engine;
 - click "ok";
 - open a new table creation window;
 - leave the "engine" field blank;
 - create some column;
 - apply the changes;
 - close the newly created table window;
 - right-click over the table at tables tree and choose "alter table";
 - check the table's engine at the very first tab.

Suggested fix:
when leaving table's engine field blank at creation, create the table with engine configured at preferences.

Indeed, looks like default storage engine from MySQL tab in Preferences does not apply to tables created in SQL Editor. Thus default engine on server is used.