MySQL Bugs: #69530: Tables with no changes flagged as changed

Bug #69530	Tables with no changes flagged as changed
Submitted:	20 Jun 2013 20:06	Modified:	21 Jun 2013 12:38
Reporter:	Rasmus Schultz	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	6.0.2 beta	OS:	Windows (8)
Assigned to:		CPU Architecture:	Any

Description:
Some tables appear as changed but the list of changes in the dialog is empty.

How to repeat:
See `collaboration` table in file attached to #68369 for example.

This one is interesting. There is an internal inconsistency in your model, the table collaboration has an index called PRIMARY, but somehow it's not marked as a Primary Key for the table. That is causing the false diff during sync. You can fix your model by issuing the following command from the Scripting Shell:

grt.root.wb.doc.physicalModels[0].catalog.schemata[0].tables[9].primaryKey = grt.root.wb.doc.physicalModels[0].catalog.schemata[0].tables[9].index[0]

(print grt.root.wb.doc.physicalModels[0].catalog.schemata[0].tables[9].name to make sure that it's really the table you want to fix, if it's not change the index for tables[] to the right value)

And then remove the PK, if you don't want a PK.

I'll mark this as Not a Bug, but if you can provide steps to provoke this inconsistency again, please reopen and we'll fix that. Thanks.

It's not unthinkable this could have happened when I was forced to manually edit the XML file inside the project archive, using a text-editor. Some bug was preventing me from making certain changes via the interface, and I had to patch things up by hand - it was a while ago, and I don't recall specifically what I did or why it was necessary.

Thanks for looking into this.