MySQL Bugs: #39481: Catalog diff report doesn't make sense

Bug #39481	Catalog diff report doesn't make sense
Submitted:	16 Sep 2008 14:54	Modified:	23 Dec 2008 13:37
Reporter:	Roland Bouman	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.0.25	OS:	Any
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
catalog diff report doesn't seem to make sense.  I get messages saying the same FK was both added and removed. (it is btw very unclear where something was added or removed - the report should explicitly specify which objects it is talking about, (left or right catalog)

How to repeat:
Action: 
1) reverse engineer from script (sakila example database schema script)
(Menu / File / Import / rev eng. sql script)
2) forward engineer to live database
(Meny / Database / Forward Engineer)
3) Generate catalog diff report
(Menu/ Database / Generate Catalog Diff Report)

Technically there should be no differences. However, it is full of things like: 

"Table X modified:
    foreign keys:
    - added foreign key Y ,,,,,
    - removed foreign key Y"

The foreign key is present in both the model as well as the database. So something is clearly wrong.

Suggested fix:
Can't determine what cause is - can't suggest fix. Expected empty diff report.

Thank you for the bug report.

I am having the same issue and it is rendering the diff report useless along with making the synchronize function confusing since it states may tables are different even though they are not.  Any time line on a fix for this?

this is actually a cuplicate of http://bugs.mysql.com/bug.php?id=38507
sync and diff-report use the same functions to compare structures, only differ on output