MySQL Bugs: #66356: Synchronize not finding differences

Bug #66356	Synchronize not finding differences
Submitted:	13 Aug 2012 16:15	Modified:	19 Aug 2012 13:05
Reporter:	David Dykstra	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.40 Revision 8790	OS:	MacOS (10.7.4)
Assigned to:		CPU Architecture:	Any
Tags:	differences, model, not working, synchronize

Description:
After getting my new computer, I installed the latest MySQL community server and got the latest MySQL Workbench. After recreating my database from a dump and opening up my model I noticed that the synchronize ability was not finding the difference between the model and the schema. It was working alright on the previous system. It will find major differences such as the creation of a new table or deletion of a table, but it will not find foreign key changes, or column changes within a table itself.

How to repeat:
Recreate database and and model from a previous system onto a new mac system

Are you tried version 5.2.41?. Thanks.

I have now tried it with 5.2.41. I am running into some oddities so I can say for sure if the problem is fixed. When I first opened the model it said I had duplicate foreign key names and renamed nearly all my foreign keys, which is odd cause I am sure I didn't have any, but I went with the process anyways. Then I ran synchronize and sure enough it found all the key name changes. It also ran into another bug where the model name is in All CAPS but the schema isn't it tried to Drop the schema first and then tried to apply the changes. This of course did not work and my schema was dropped. Smart of me I restored from a back up I made right before this process began. So I tried it again this time I renamed my model to match the name of the schema. When I went to synchronize it warned me of the model rename saying it would have to rename the schema by dropping and creating the schema from scratch, I definitely told it to ignore this. I proceeded and It successfully synchronized. Great, I thought, until I restarted the application only to find that none of the changes were actually made on the schema, It only pretended it was completed. So at this point I will say that things changed in the upgrade, however more bugs have now been exposed. Until this is fixed I will not use this feature, ever.

Okay, So I was able to fix the foreign key problem. Apparently the process that MySQL WB went through in renaming all my indices was the problem. For some reason it figured that because the fk constraint and the name of the index were the same, it add _idx to the end of all my indices. After manually deleting all these _idx I then ran the synchronize and it actually worked this time. So that solved one of the issues

After fixing the oddities caused by the upgrade, I am able to state that this bug no longer exists. The synchronize tool now picks up small changes to the model and synchronizes correctly.

Not repeatable with recent versions.