MySQL Bugs: #56970: Synchronize database doesn't syncrhonize

Bug #56970	Synchronize database doesn't syncrhonize
Submitted:	23 Sep 2010 14:00	Modified:	27 Sep 2010 19:27
Reporter:	Renato Lipi	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.28	OS:	Linux (2.6.32-31-generic Ubuntu)
Assigned to:		CPU Architecture:	Any
Tags:	syncrhonize

Description:
I have this .mwb file, where I have some tables. It happen sometimes, I didn't figure out why or when yet, and it seems to be randomic to the table:
I just finished synchronizing a "foo" table, when I go to "synchronize database" again (and didn't modified this "foo" table), it shows me there is a synchronizing to do on this table. But it's not true. It is already the same as in the database. 

How to repeat:
I don't know yet. It occurs each time in different tables. I'll try to make an example that can repeat this.

Suggested fix:
No idea.

More info on what is happening:

I found out that MySQL Workbench (M.W.) didn't have changed some table default values, I mean, there were default values that M.W. didn't changed on the database(according to my modeling file) and it should have synchronized. That's why it always said I had a missing sync to do, because the db default values were not changed as indicatad at my modeling file.

What did I do?

I updated my modeling file (.mwb) from the database (synchronized it "backwards"). As I had no modifications to do, it simply stopped showing there was a sync to do.

About bug reporting:

Should I close this report (really sorry) or it is still a kind of bug, since M.W. didn't made the changes I asked to change?

Please, send .mwb file with initial model, then describe what default values should be changed. This should allow us to check if there is a bug here.

I got no way to reproduce it constantly, so I'm closing this bug report. I'll post another one, later, that I can reproduce it always. Let me check it is already reported before.