Bug #35867 Relationships should not be drawn over tables (at least not by default)
Submitted: 7 Apr 2008 9:01 Modified: 11 May 2008 1:31
Reporter: Roland Bouman Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.0.16, 5.0.17 (OSS and SE) OS:Windows (XP)
Assigned to: Alfredo Kojima CPU Architecture:Any

[7 Apr 2008 9:01] Roland Bouman
Description:
[2008-04-07 10:40] <roland> mikez: but what is totally beyond me is why ever WB decides to draw relationships over the tables
[2008-04-07 10:40] <mikez> roland, that is a bug
[2008-04-07 10:40] <roland> mikez: I can't really think of a single instance where i'd want to do that
[2008-04-07 10:41] <roland> mikez: ok
[2008-04-07 10:41] <mikez> it should be a quick fix
[2008-04-07 10:41] <roland> mikez: is it know already or should it filed?
[2008-04-07 10:41] <roland> *known*
[2008-04-07 10:41] <mikez> please file a short bug report and immediately assign it to alfredo
[2008-04-07 10:41] <roland> ok
[2008-04-07 10:41] <mikez> he will be able to fix that today

How to repeat:
just import a largish model with FK's

Suggested fix:
Don't draw relationships over tables by default. I am not opposed to allowing people to control the stacking order using the arrange menu, but IMO, the default behaviour should be to *not* draw relationships over tables.
[7 Apr 2008 13:26] MySQL Verification Team
Thank you for the bug report.
[2 May 2008 8:24] Johannes Taxacher
thats fixed in release version 5.0.21, Rev 3111
[11 May 2008 1:31] Paul DuBois
Noted in 5.0.22 changelog.

Relationships were drawn over tables.