MySQL Bugs: #46581: Reverse engineering doesn't create foreign keys on large databases (150+ tables)

Bug #46581	Reverse engineering doesn't create foreign keys on large databases (150+ tables)
Submitted:	6 Aug 2009 7:52	Modified:	6 Sep 2009 8:56
Reporter:	Petr Burian	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.1.16	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	foreign keys, reverse engineering

Description:
When importing large database with e.g. 150 tables Workbench doesn't create foreign keys. We found interesting this is only (probably) a windows version problem. In linux version of Workbench we can import our database quite well.

Other minor problem of this bug are random Workbench crashes when working with corrupted import schema (without foreign keys).

How to repeat:
We can't provide you with data model right now (maybe in near future). But see the attached screens. Windows screen is broken. Linux screen (yes this is in windows Workbench but imported in linux version!) is alright.

Again this bug doesn't appear on small databases (up to 50 tables) but on large databases (150+ tables) this is an issue.

Reverse Engineering of windows Workbench version - broken

Attachment: reverse_win.jpg (image/jpeg, text), 488.13 KiB.

Reverse Engineering of linux Workbench version - alright

Attachment: reverse_linux.jpg (image/jpeg, text), 224.61 KiB.

Could you verify that it's namely foreign keys (not just relations) what is not created?
Please check if 'foreign keys' tab in table editor is really empty for referencing tables.

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".