MySQL Bugs: #62595: Synchronize model doesn't want to sync modified stored procedures

Bug #62595	Synchronize model doesn't want to sync modified stored procedures
Submitted:	1 Oct 2011 21:02	Modified:	13 Nov 2012 4:56
Reporter:	Michael Beaucourt	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	5.2.34, 5.2.35	OS:	MacOS (Mac OS X 10.6.8)
Assigned to:		CPU Architecture:	Any

Description:
At this moment I have a model with 3 schemas. One of the schemas has about 8 stored procedures. When I synchronize the model, it suggests to sync 3 stored procedures which have NOT been modified (over and over again when trying synchronizing). One of the modified stored procedures however is NOT being suggested. So the only way to get the stored procedure on my DB is to Forward Engineer my database again.

How to repeat:
At this moment, everytime I try to synchronize the model, it 'refuses' to update the  modified stored procedure. The suggestion of not modified SPs started a lot earlier when designing the model, but it didn't hinder my progress, so I did not care too much. Now I am unable to properly update my database server.

Suggested fix:
It would be nice if the replacement of a stored procedure could be forced. Now, if the function 'Synchronize model' doesn't see a difference in the code, it won't do anything, even if I select 'Update source'. It should be able to replace a SP if the user says so.

Can you provide a model (.mwb file) that demonstrates this problem? What exact server version, x.y.z, are you working with.

FYI: At this moment, the workaround I am using is 'Forward Engineer' with 'Drop objects' selected. I then only select the modified stored procedures.  But 'Synchronize model' would have been more convenient to use.

Verified with your .mwb file uploaded in private. Indeed, immediately after froward engineering and without any changes applied Workbench still suggests to sync `hrm`.`GetVerlofJaren` procedure when I try to synchronize model...

Fixed as of the upcoming MySQL Workbench 5.2.45, and here's the changelog entry:

Sometimes a modified stored procedure would not be flagged as modified
while synchronizing a model.

Thank you for the bug report.