Bug #34457 Autoplace when reverse engineering a database dosn't display all tables
Submitted: 11 Feb 2008 13:00 Modified: 14 Feb 2008 20:35
Reporter: Vicente Werner Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.13 OS:Any
Assigned to: CPU Architecture:Any
Tags: autoplace, bugs, reverse engineering

[11 Feb 2008 13:00] Vicente Werner 
Description:
This is an extension to #34350. I've found that the problem dosn't lie on the reverse engineering part, but on the autoplace function. 
Autoplace tries to place as many tables as it can on the page, but using only half the defined page (divided vertically into two), and when it arrives at the botton of the page stops putting new tables although it has the other half of the page to continue placing the remaining ones.

How to repeat:
Reverse Engineer a database with many tables (40 should do) with Autoplace activated.
Once the database is loaded, check the model and you'll see that not all the tables imported have been placed  on the model, the remaining ones show on the Catalog window and can be added manually.
[12 Feb 2008 4:25] Valeriy Kravchuk 
Thank you for a bug report. Verified just as described.
[14 Feb 2008 20:35] Johannes Taxacher 
actually this _is_ the the same as described in bug #34350