MySQL Bugs: #43446: Edit relationship lines in diagram in both directions

Bug #43446	Edit relationship lines in diagram in both directions
Submitted:	6 Mar 2009 9:45	Modified:	4 Aug 2009 0:01
Reporter:	Dimitri van Hees	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S4 (Feature request)
Version:	5.0.30	OS:	Windows (Vista Ultimate Edition)
Assigned to:		CPU Architecture:	Any
Tags:	CHECKED, model, relationship

Description:
I would like to be able to drag relationship lines in the diagram in both directions, top to bottom AND left to right. I entered this 'bug' in the beginning when using the OS edition and hoped it was able in SE but unfortunately it isn't. I am unable to create arranged models with a lot of tables because there is only one marker per relationship line available to drag it either from left to right OR from top to bottom and vice versa.

How to repeat:
Create more than one table with a foreign key to another table and place them on a diagram. Only one direction (horizontal OR vertical) of the relationship line can be dragged.

To move the relationship in different direction you have to drug one of the tables. I think it is reasonable, as soon as we fix the relationship line at the side of the rectangle representing table.

This is not a reasonable option when there are many tables. Besides, dragging the table only results in dragging the line the other direction, but still not both. I would like to be able to route the lines myself. As this is a feature request, I hope the developers will have a look at the way MS Visio handles connection lines ;-)

I fully agree with the reporter; and I also agree this is more like a feature request than a bug, but i would LOVE to have more options in drawing the relationships. I too work with loads of tables and placing them nicely without crossing lines is an absolute annoyance. It leaves me working on the models longer than I can afford to.

I hope this will be solved in the near future. besides this problem workbench is great!

(incorrectly set to Documenting)
This bug is the same issue as #33803