MySQL Bugs: #34546: Foreign key display across multiple schemas

Bug #34546	Foreign key display across multiple schemas
Submitted:	14 Feb 2008 14:40	Modified:	11 May 2008 1:40
Reporter:	Yuri Alekseyev	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.0.13	OS:	Windows (XP SP2)
Assigned to:	Alfredo Kojima	CPU Architecture:	Any

Description:
Several issues with setting up foreign keys across multiple schemas:

1. Setting relationship is possible only in diagram mode as the manual foreign key control shows only tables within the same schema and does not allow manually modifying the parameter.

2. Diagram mode does not display correctly such relationships.

How to repeat:
1. Self-explanatory.

2. For example we have table `schema1`.`a` and `schema2`.`b`, each in its own schema. `schema1`.`a` have parent PK column `aID` whereas `schema2`.`b` have `aID` as a foreign non-identifying key referencing to `schema1`.`a`.`aID`. To make relation visible in diagram we have to put `schema1`.`a` first on the board and only then `schema2`.`b`, otherwise it will not show. Additionally it crashes the application if you select and remove both tables and visible relation from the diagram.

SQL-script to reproduce the problem

Attachment: create_34546.sql (application/octet-stream, text), 1.15 KiB.

The crash and the placement bugs are fixed. The table editor problem is still pending.

all issues mentioned in this report are fixed. tested with svn rev 3126.
it's now possible to select tables fom different schemata in the referenced table dropdown boxes.

Noted in 5.0.22 changelog.

Setting up foreign key relationships across multiple schemas did not 
work.

does workbench (SE edition) handle cross-schema foreign key?
with live synch i tried to import two schemas but workbench seems unable to re-create cross-schema fk. am I right?