MySQL Bugs: #40997: Workbench not highlighting foreign key relationship in EER Diagram

Bug #40997	Workbench not highlighting foreign key relationship in EER Diagram
Submitted:	25 Nov 2008 3:29	Modified:	25 Aug 2010 11:48
Reporter:	Christopher Vrooman	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.27	OS:	Windows (XP, SP3)
Assigned to:	Mike Lischke	CPU Architecture:	Any
Tags:	foreign key, highlight, relationship

Description:
I was clicking on foreign on the dashed Relationship identifiers when one happened to *NOT* highlight, while the rest did. The foreign key happened to be the last field visible before the "Indexes". Further experimentation led to the following:

1. It appears to only happen when the foreign key is the last field (because the previous field was also a foreign key and that did highlight the relationship.

2. This only occurs when there is not enough "space" below the field between it and the "Indexes" label.

3a. If I resize the table and add more space below the field, then it will highlight the relationship like any other foreign key.

3b. If I click on the Indexes toggle and show the existing indexes, the foreign key will now highlight. Collapsing the indexes disables the highlighting once again.

How to repeat:
Create a foreign key relationship.

Move the foreign key to end of the list of fields.

In the EER Diagram, resize the table with the foreign key so that it is just visible/partially covered by the "Indexes" divider/toggle.

Position the cursor over the dashed relationship connector.

It should *NOT* highlight.

Suggested fix:
Revisit the highlight rendering mechanism and relax the constraints of showing a field as highlighted when partially/almost covered by the Indexes toggle.

Thank you for a problem report. Please, send the .mwb file to illustrate the problem.

Thank you for the feedback.

hello chris, could you check if that has something to do with the zoom level? the diagram in the doc you submitted is zoomed at 81%.  I could not repeat the problem following your description, but I ran into the problem when trying adifferent approaches. According to my abservations this is connected to the zoonlvl of the canvas. can you confirm that?

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".

Thank you for your bug report. This issue has already been fixed in the latest released version of that product, which you can download at

  http://www.mysql.com/downloads/