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: | |
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
[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.