| Bug #45868 | Detection of differences in synchronization | ||
|---|---|---|---|
| Submitted: | 1 Jul 2009 5:05 | Modified: | 5 Feb 2013 18:44 |
| Reporter: | Pavel Dobryakov | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | MySQL Workbench | Severity: | S2 (Serious) |
| Version: | 5.1.16 | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[1 Jul 2009 5:05]
Pavel Dobryakov
[2 Jul 2009 4:17]
Valeriy Kravchuk
Thank you for the bug report. Indeed, if you'll try to synchronize model with database two times in a row you'll see that WB tries to re-create stored function even if it had NOT changed.
[9 Jul 2009 12:41]
Susanne Ebrecht
The workaround is to synchronise from database.
[25 Feb 2010 20:39]
Ćukasz Dejneka
It's even weirder for me, on MySQL Workbench 5.2.15 OSS, Revision 5053... I have 3 stored procedures and 2 of them always update, even if there is absolutely no change to them, while one does not want to synchronize even when I edit it. What's worse, when I force (or at least try to force) the update, by assigning the green arrow in the "Select changes to apply" section of "Synchronize model with database" dialog, for that stored procedure, it still does not incude it in the update code produced. Basically I need to drop the procedure each time on the server so I can update.
[7 Oct 2010 14:34]
Edward Rudd
This issue still occurs in 5.2.28 and is very frustrating, as I can't reliably update my working copy of the DB's stored functions and procedures.
[2 Feb 2011 7:32]
Pavel Dobryakov
This issue still occurs in 5.2.31 and is impeding introduce the use of workbench on any major projects.
[5 Feb 2013 18:44]
Alfredo Kojima
Closing old bug, this has been fixed previously.
