MySQL Bugs: #55147: synchronize model does not show schemas to select

Bug #55147	synchronize model does not show schemas to select
Submitted:	10 Jul 2010 2:27	Modified:	24 Sep 2010 15:17
Reporter:	Tim Vazquez	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.25	OS:	MacOS (10.5.8)
Assigned to:	Alexander Musienko	CPU Architecture:	Any
Tags:	model, sychronize

Description:
when the wizard gets to the  "Select Schemata" section, there are no schemas to select

How to repeat:
open EER diagram
select Database > Synchronize Model
select connection
when wizard show "select schema" page, there are no schemas

Screenshot showing that there are no schemas to select

Attachment: Picture 1.png (image/png, text), 55.13 KiB.

This error is being caused by the schema name having capital letters in the EER model and not having them on the server.

EER Model schema name = "MYSoftware"
Server name = "mysoftware"

changing the EER model to all lowercase letters resolves my issue.

in version 5.2.1 the difference in capitalization did not matter.

Please, send the results of:

show variables like '%lower%';

from your MySQL server. Are you sure they were the same when you had used older version of Workbench?

lower_case_file_system: ON
lower_case_table_names: 1

The only thing that has changed in my setup is the version of workbench.
I started with v5.2.1 and had no problem syncing my DB. Every version since has given me this error. I reversed engineered my db with 5.2.25 and noticed the difference in case. I then changed the EER Diagram schema to match this case and 5.2.25 worked.

From now schemas list is taken from model. So that you may sycn schema if it is already in DB or it can be created othervise.

fix confirmed in release 5.2.27

An entry has been added to the 5.2.27 changelog:

When an attempt was made to synchronize a model with a live database, no schemata were listed as available in the Synchronize Model with Database wizard. This happened when the name of the schema in the model and the schema on the live server were only differentiated by case.