Bug #49568 Engine name not seen when Create EER Model from SQL script
Submitted: 9 Dec 2009 16:50 Modified: 26 May 2010 10:26
Reporter: Nidhi Shrotriya Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.10 OS:Linux (ubuntu 9.04)
Assigned to: Sergei Tkachenko CPU Architecture:Any

[9 Dec 2009 16:50] Nidhi Shrotriya
Installed workbench 5.2.10 from http://dev.mysql.com/downloads/select.php?id=8 on Ubuntu

Launched mysql-workbench.

Home -> Create EER Model from SQL script ->
where table creation statements contain engine = innodb

Click on table in EER diagram 
Engine name 'innodb' is not seen selected.

How to repeat:
As mentioned in description.
[9 Dec 2009 21:43] MySQL Verification Team
Thank you for the bug report.
[22 Apr 2010 1:18] Alfredo Kojima
The problem happens only when the case of the engine name does not match the expected one (ie, it works ok when the engine is InnoDB but doesnt for innodb)
The Import wizard should perform a post-processing step, where normalization of such things is performed and other checks could be added in the future.
[25 May 2010 23:19] Johannes Taxacher
fix confirmed in repository
[26 May 2010 10:26] Tony Bedford
An entry has been added to the 5.2.22 changelog:

When using Create EER Model from SQL Script from the Home screen, the specified engine type was not present in the resultant EER model.