MySQL Bugs: #51505: Docking Points of Relationships in EER Diagrams should be user changable

Bug #51505	Docking Points of Relationships in EER Diagrams should be user changable
Submitted:	25 Feb 2010 14:14	Modified:	4 Apr 2014 14:17
Reporter:	Kai Sautter (Basic Quality Contributor)	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S4 (Feature request)
Version:	5.2.16	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	qc

Description:
If tables have a larger number of relationships, routing of relationship lines between tables makes reading the diagram rather complex, as
- lines flow under table boxes
- unnecessary bridges (2 crossing lines) are generated.

Given the fact, that automated routing would need to be based on complex algorithms, to avoid this, it might be helpful to allow the user to change the sequence of docking points for individual relationships of a table or to even freely define the docking point.

Furthermore it might be helpful to allow the user to not only shift a transversal part of a relationship (middle part if it is a z-like line), but also to add additional bends.

How to repeat:
Feature request.

Suggested fix:
see description for first ideas.

Thank you for the feature request.

We second the request. Please include a feature which would allow us to add more bends to the relationship lines.

I'll add my vote for this request as well. [Only] when there are three line segments for a relationship, the middle segment has a handle that allows the user to move that segment perpendicular to its direction. By adding handles to all the line segments, regardless of how many line segments there are (1, 2, or 3), relationship lines can be adjusted to fit almost any situation.

This request has gained urgency. I upgraded from 5.2.35 to 5.2.37 and found that ERD diagram objects shifted from their previous positions. Although the shifts were slight, they resulted in shifts in the position of certain relationship lines and, in some cases, redrawing the relationship lines such that they now travel through entity diagrams. 

I attached a zip of two .mwd files; version 2e, last updated with 5.2.35; and version 2f, as it was opened with 5.2.37. This is a very tight diagram with a carefully choreographed object layout such that no relationship lines intersected an entity object with which it isn't connected. The shifts that occurred with version 5.2.37 irreparably harm that choreograph.

File Bug 51505.zip was uploaded to ftp://ftp.oracle.com/support/incoming/ to document my previous comments.

duplicate of Bug #33803