Bug #70345 | Workbench drops schema on source when updating model | ||
---|---|---|---|
Submitted: | 14 Sep 2013 18:04 | Modified: | 26 Sep 2015 21:24 |
Reporter: | Joe Brown | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S1 (Critical) |
Version: | 5.2.47 | OS: | Windows |
Assigned to: | CPU Architecture: | Any |
[14 Sep 2013 18:04]
Joe Brown
[19 Sep 2013 12:23]
Lisa Ehrlinger
Hi Joe, I wasn't able to reproduce this behaviour. Could you please provide more information about what WB Version and OS you use and the model you wanted to update?
[19 Sep 2013 18:17]
Joe Brown
I think I might know a repro. After the model was initially created, somebody added a foreign key to a different database. When the model was synchronized again, the model became aware of the other database. The synchronize was not fully run, so that the new schema was not created. Upon subsequent sync's, the model started offering to drop the schema on the source server. Here's my version info: MySQL Workbench CE for Windows version 5.2.47 revision 10398 Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE Cairo Version: 1.8.8 OS: Microsoft Windows 7 Enterprise Edition Service Pack 1 (build 7601), 64-bit CPU: 4x Intel(R) Core(TM) i7-3520M CPU @ 2.90GHz, 7.7 GiB RAM
[26 Aug 2015 21:24]
MySQL Verification Team
Please try version 6.3.4. Thanks.
[27 Sep 2015 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".