| Bug #80516 | MySQL Workbench cannot reverse engineer ER Diagram with 730 tables | ||
|---|---|---|---|
| Submitted: | 25 Feb 2016 12:33 | Modified: | 23 Jan 2017 20:34 |
| Reporter: | Oli Sennhauser | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
| Version: | OS: | Windows (10) | |
| Assigned to: | CPU Architecture: | Any | |
| Tags: | er-diagram, reverse engineer, workbench | ||
[25 Feb 2016 12:33]
Oli Sennhauser
[25 Feb 2016 12:44]
Oli Sennhauser
create test case
Attachment: create_1k_tables.php (application/x-httpd-php, text), 1.22 KiB.
[25 Feb 2016 16:58]
MySQL Verification Team
error dialog
Attachment: reverse_eng.png (image/png, text), 160.06 KiB.
[25 Feb 2016 17:05]
MySQL Verification Team
Thank you for the bug report. I wasn't able to find in documentation such limitation anyway sounds for me a feature request.
[26 Feb 2016 8:17]
Mike Lischke
What this message is about is that Workbench wants to prevent you from placing 1000 tables on a single diagram *during reverse engineering*. You can always split this set over multiple diagrams (which would make more sense from a structural point of view anyway) or you can add more tables to the new diagram after the RE process. However, you can still reverse engineer everything. IMO this report is neither about a bug nor a feature request, but simply a misunderstanding and should therefore be closed.
[18 May 2016 23:27]
Philip Olson
Posted by developer: Did something change here? Also, long ago I provided a StackOverflow response to a similar issue: http://stackoverflow.com/questions/27700967/mysql-workbench-too-many-objects-are-selected-... Is the answer there (still) the recommended approach to this situation? As stated, I did test it with 2000 tables.
[23 Jan 2017 20:34]
Christine Cole
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.3.9 release, and here's the changelog entry: Selecting too many tables when attempting to reverse engineer an EER diagram caused MySQL Workbench to fail and exit. This fix sets the permitted threshold to 1000 objects and displays a warning message when the number of objects exceeds the threshold. Thank you for the bug report.
