Bug #89530 | Relationships not showing after reverse-engineer | ||
---|---|---|---|
Submitted: | 5 Feb 2018 9:53 | Modified: | 5 Feb 2018 13:48 |
Reporter: | Arthur Attout | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 6.3 CE, 6.3.10, 8.0.36, 8.0.38 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | relationships;lines |
[5 Feb 2018 9:53]
Arthur Attout
[5 Feb 2018 10:03]
Arthur Attout
I managed to import a SQL script and show the relationships BUT I had to create a new model BEFORE, and then import data in it, instead of using the option "Create EER model from Script". This seems to be a completely different bug.
[5 Feb 2018 11:58]
MySQL Verification Team
Hello Arthur, Thank you for the report. I'm not seeing any issues with dummy test case, observed that relationships are properly mapped after importing. Could you please attach the script here to confirm the issue at our end? I assume that you are using latest GA WB build. Thanks, Umesh
[5 Feb 2018 13:17]
Arthur Attout
Hello ! Here is the file I have used https://pastebin.com/9515AxCU Here are the steps to reproduce the issue : Scenario with bug : On the main menu, in the "models" tab, use the arrow to show the options, and click "Create EER Model from script" Check "place imported objects on a diagram" Click Execute The relationships are not shown _____ Scenario without bug : Click "File > new model" In the model tab, click "File > import > Reverse engineer MySQL Create Script" Check "place imported objects on a diagram" Click Execute The relationships are successfully shown
[5 Feb 2018 13:48]
MySQL Verification Team
Thank you for the requested details. Verified as described. Thanks, Umesh
[5 Feb 2018 13:48]
MySQL Verification Team
Reduced sql script file
Attachment: bug.sql (application/octet-stream, text), 713 bytes.
[19 Apr 2024 5:23]
MySQL Verification Team
Bug #114688 marked as duplicate of this one.
[26 Jul 2024 12:31]
MySQL Verification Team
Bug #115694 marked as duplicate of this one.