MySQL Bugs: #55942: WB synchronize with different schema failed

Bug #55942	WB synchronize with different schema failed
Submitted:	12 Aug 2010 11:51	Modified:	12 Aug 2010 11:59
Reporter:	Csaba Bukor	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.26	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	synchronize

Description:
We have 3 schema: Developement, live, test. 
I would like to use one model to synchronize the databases. 
I've already know that for sync WB needs the same case sensitive schema names (I don't understand why wb needs this kind of restrictions?). 
My model schema name: dev_sanofi, which is the development project. 
I try to sync the test system, so I modified the model's schema name to teszt_sanofi.
When the differences window appeares I saw 2 lines:
1.: Model: teszt_sanofi, Source: N/A
2.: Model: N/A, Source: teszt_sanofi

How to repeat:
It will happen if you modify the schema name in the model and try to sync it.

Suggested fix:
WB can sync with different schema names.

Workbench 5.2 does not support synchronization of a model to multiple target schemas. As in your case  WB currently recognizes the renaming of the schema inside the model as change to the DB-model and therefore doesn't recognize the "new" target schema as identical (as it searches for a model with the old name). We plan to improve/extend that functionality in future versions of MySQL Workbench.

this is a duplicate of Bug #38869