Bug #54892 Synchronize Schema wizard blocks on Select Schemata
Submitted: 29 Jun 2010 9:29 Modified: 25 Aug 2010 1:11
Reporter: Daniël van Eeden Email Updates:
Status: Duplicate Impact on me:
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.24 OS:Any
Assigned to: Alfredo Kojima CPU Architecture:Any

[29 Jun 2010 9:29] Daniël van Eeden
1. Open a Model
2. Click Database
3. Click Synchronize Model
4. Select a Stored Connection and click Next
5. Both "Connect to DBMS" and "Retrieve Schema List from Database" are successful
6. Click next
7. Now there is a screen with "Select the Schemata to be Processed:" but there are no options available.

How to repeat:
See description

Suggested fix:
Check if there are any options available and if not print a useful help message and/or debug info.
[29 Jun 2010 9:54] Valeriy Kravchuk
There are many similar reports. Bug #54748 is one of the recent examples.
[29 Jun 2010 10:56] Daniël van Eeden
This is not a duplicate of bug #54748 as that is about a case when reverse/forward engineer should've been used. This case is about a previously reversed engeneered model about an existing database.

When reverse engineering (a while ago with a 5.0 version) the schema name was set to MyDB and not to the real schema name. 

There should've been an error like this: "Error there was no schema found named 'MyDB'"
[29 Jun 2010 12:27] Valeriy Kravchuk
Whatever the origin of your schema, what schema name is used in .mwb file and do you have database with the same name on your MySQL server that you try to synchronize with?
[9 Jul 2010 12:49] Daniël van Eeden
This is when the schema name in the .mwb file is not available in the MySQL instance to which it connects.

There should be a error message like this:
"MySQL Workbench could not find a schema named '%s', Please make sure the schema name in your model is the same as the schema name on the MySQL Server."
[25 Aug 2010 1:11] Alfredo Kojima
This is a duplicate of bug #54748, the origin of the database does not matter. If the schema name doesn't exist in the server, the problem will occur.