MySQL Bugs: #49044: Table creation in WB doesn't support engine-specific details

Bug #49044	Table creation in WB doesn't support engine-specific details
Submitted:	24 Nov 2009 17:29	Modified:	10 Aug 2012 4:04
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Won't fix	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2 r4753	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any

Description:
When creating tables in WB which require (or support) additional CREATE options, WB does not prompt for or support these options.  For example, FEDERATE tables require a connection to be defined, but there is no mechanism for doing so, and the SQL script which WB creates subsequently fails:

Message Log:

ERROR 1432: Can't create federated table. The data source connection string '' is not in the correct format

SQL Statement:

CREATE  TABLE IF NOT EXISTS `test`.`fed` (

  `idfed` INT NOT NULL ,

  PRIMARY KEY (`idfed`) )

ENGINE = FEDERATED

COMMENT = 'TEST'

How to repeat:
Try to create a FEDERATED table using the WB wizard.

Suggested fix:
Make WB aware of engine-specific CREATE TABLE options, at least for MySQL-produced storage engines.

Federated engine is no longer supported by server