Bug #85527 Upgrade to Workbench 6.3.9 Appears to Resolve Malfunction
Submitted: 17 Mar 2017 19:42 Modified: 20 Mar 2017 15:49
Reporter: Jason Franklin Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:6.3.8 OS:Windows (Windows 10 Enterprise, v1607)
Assigned to: CPU Architecture:Any
Tags: create script, modeling, workbench

[17 Mar 2017 19:42] Jason Franklin
Description:
In an attempt to document a database for my employer, I used `mysqldump` to extract the schema from a MySQL v5.5.43 server and attempted to load the schema into a new model created with Workbench using "File | Import | Reverse Engineer MySQL Create Script".

Though the import procedure reported no errors, I was expecting 65 tables to be created in the model, with one model table object corresponding to each physical table in the database.  However, I was surprised to see that 10 tables were not included in the resulting list of imported tables.

What is even more surprising is that an attempt to load the same script into the development server running locally on my machine results in the expected 65 tables, with no detectable errors.

I can find no indication that this error has been reported before.  It could be a character set issue or some other simple problem (I'm only mildly experienced with MySQL at this point).

To summarize the versions of the software involved:
  * MySQL Server v5.5.43 (on the server)
  * MySQL Server v5.7.14 (locally, running on Windows 10)
  * MySQL Workbench v6.3.8 (locally, running on Windows 10)

How to repeat:
Repetition of the bug is difficult without providing my entire script (too long for here, sections can be provided on request).

It should be noted that I have difficulty repeating the bug reliably.  If, for example, I remove all CREATE TABLE statements save for one that was originally omitted and then try to import the schema again, the script that was omitted will now be visible as the only script.  This is surprising since it was previously left out.

Suggested fix:
I'm hoping that this is not, in fact, a bug, and that I will be able to make some minor adjustment and keep moving along. A pointer to documentation that may exist that addresses this issue would be welcome.  Searching for it has been difficult however.
[19 Mar 2017 20:41] MySQL Verification Team
Thank you for the bug report. Please try version 6.3.9, if you still get the same issue then provide a test case which contains 2 or more not imported table so we can repeat it on our side (attach the test case private if you wish using the Files tab). Thanks.
[20 Mar 2017 14:17] Jason Franklin
Hi Miguel,

I performed the recommended upgrade to version 6.3.9 of MySQL Workbench and all tables are now being imported successfully (all 65 for the original database, as well as 66 for the additional test database).  I am pleased with the result.

Out of curiosity, is there any hint as to what caused the problem?  I could find no instances of this issue elsewhere.  

In any case, thanks for your advice.

Jason
[20 Mar 2017 15:49] MySQL Verification Team
Thank you for the feedback. I don't have a clue for the reason of issue in prior version, anyway glad to read current version worked.