Bug #82151 Model Synchronisation not working properly
Submitted: 7 Jul 2016 14:38 Modified: 25 Apr 2018 17:29
Reporter: Micaël Pais Novo Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.3.10 OS:Windows (Windows 10 64-bit)
Assigned to: CPU Architecture:Any
Tags: functions, model, schema, stored precedures, sync, synchronisation, UPDATE

[7 Jul 2016 14:38] Micaël Pais Novo
Description:
We are experiencing an issue with the model synchronisation feature. When we start a synchronisation between two schemes, the tables are correctly compared, but the stored procedures and functions are always shown as "Updated".

For example, I have two stored procedures and two function to synchronise in development and production servers. Even thought they are identical in the two servers, Mysql Workbench indicates that the development server has new changes  and can update the production server. Strange thing is that when I do what Mysql Workbench tells, the functions stop to work. The only way to workaround this is to copy paste code between servers.

This issue does not exist with older Mysql Workbench versions (I reinstalled 6.2.3 and it works fine). The two servers are running Mysql Server 5.5.43-0+deb7u1.

How to repeat:
1- Create identical stored procedures and functions in two servers
2- Try to Synchronise Models (from Database > Synchronise Model)
3- The stored procedures and functions should be marked as updated. Accept and synchronise models
4- Repeat step 2
5- The stored procedures and functions are still marked as updated. Moreover, the function stop to work
[8 Feb 2017 20:16] MySQL Verification Team
Please try version 6.3.9. Thanks.
[13 Feb 2017 9:16] Micaël Pais Novo
Hello,

The problem is still persistent. 

We found a workaround : check "Skip checking of routine definer", 
although the definers are exactly the same between the two databases.

Do you have any idea ?
[12 Dec 2017 17:12] MySQL Verification Team
Thank you for the feedback. Please provide the model file so we can test with version 6.3.10 (use Files tab for). Thanks.
[13 Jan 2018 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[17 Jan 2018 12:54] Micaël Pais Novo
Hello,

Sorry for the late answer. See attached models. This bug is still happening with Mysql Workbench 6.3.10.

We found an other workaround that seems to work : instead of using "Synchronize model" option, we now use "Synchronize with any source" selecting "Live database option".

Please let me know if you need more information.

Best regards
[24 Jan 2018 12:16] Chiranjeevi Battula
Hello Micaël Pais Novo,

Thank you for the feedback.
Verified this behavior on MySQL Workbench in 6.3.10 version.

Thanks,
Chiranjeevi.
[24 Jan 2018 12:17] Chiranjeevi Battula
Screenshot

Attachment: Bug_82151.PNG (image/png, text), 92.54 KiB.

[25 Apr 2018 17:29] Christine Cole
Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.12 release, and here's the changelog entry:

When two schemas were compared with Synchronize Models (from the Database
menu), differences were reported consistently for stored procedures and
functions even though the compared items were identical.

Thank you for the bug report.