Bug #66246 | 'original schema not found' when sync'ing. | ||
---|---|---|---|
Submitted: | 7 Aug 2012 15:39 | Modified: | 4 Mar 2013 16:56 |
Reporter: | Robert Cesaric | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Workbench | Severity: | S2 (Serious) |
Version: | 5.2.41 | OS: | MacOS |
Assigned to: | CPU Architecture: | Any |
[7 Aug 2012 15:39]
Robert Cesaric
[16 Aug 2012 14:49]
Alfredo Kojima
Are you saving the model after synchronization?
[16 Aug 2012 14:54]
Robert Cesaric
Yes. I saved, closed, re-opened, rinsed and repeated. Tried everything I could think of before actually editing the MWB xml source.
[16 Aug 2012 15:01]
Alfredo Kojima
Are the servers you synchronize with different each time or always the same one?
[16 Aug 2012 15:09]
Robert Cesaric
Same one. It's a local instance on my computer: ➜ ~ mysql5 -v Server version: 5.1.63 Source distribution
[14 Sep 2012 0:00]
MySQL Verification Team
Please try version 5.2.43. Thanks.
[1 Oct 2012 17:49]
Robert Cesaric
Sorry, I missed testing this in 5.2.43 but I just tested this in 5.2.44. Still getting the same issue. Here's the message when I try to synchronize: The schema 'demo_shop2' seems to have been renamed from '' in the model, but the original '' was not found in the RDBMS. However a schema called 'demo_shop2' seems to exist there, would you like to force synchronization with it? The schemata from your model are missing from the target RDBMS server. If you are creating them for the first time use the Forward Engineer function. I wanted to make sure my Mac upgrade to Mountain Lion had nothing to do with it so I've reverted back to 5.2.40 and repeated the test with no issue.
[1 Oct 2012 17:53]
Robert Cesaric
Also, I just downloaded 5.2.43 and tested. Still same issue as with my 5.2.44 tests above.
[9 Nov 2012 2:37]
James Hayes
Just wanted to chime in and say that I'm experiencing this issue on 5.2.44 as well, but on Windows 7 x64 for a remote database.
[22 Jan 2013 12:44]
MySQL Verification Team
I can't repeat with Mountain Lion on MacBook Pro and remote server on Windows 7. Please provide the Workbench project file. Thanks.
[22 Jan 2013 18:05]
Robert Cesaric
MWB file that reproduces force sync message.
Attachment: MySQL_Bug.mwb (application/octet-stream, text), 5.19 KiB.
[4 Mar 2013 16:56]
Alfredo Kojima
A few things: - if you're creating a new DB on a server, you should use Forward Engineer, not Synchronize - after the 1st time I synchronize by forcing it (which would not be necessary if you use Forward Engineer), any new synchronizations I do afterwards to the same DB work just fine So it looks like this is not a bug.