Bug #64764 Created schema reverts to 'new_schema' when 'Default Collation' selected
Submitted: 26 Mar 2012 13:02 Modified: 2 Apr 2012 13:17
Reporter: billy s Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S3 (Non-critical)
Version:5.2.38 OS:MacOS (10.5.6)
Assigned to: CPU Architecture:Any
Tags: schema

[26 Mar 2012 13:02] billy s
Description:
When I try to create a new schema using the 'Create a new schema in the connected server' icon, no matter what I use as the 'Schema Name', as soon as I select a collation from the dropdown, the schema name field reverts back to 'new_schema'. If a user is not careful to recheck all fields before they click 'Apply', a schema named 'new_schema' will be created rather than with the name they desired.

How to repeat:
Open a database connection, and in the menu of icons under the connected server tabs, click the third from the left (labeled 'Create a new schema in the connected server'). Type anything in the 'Schema Name' field (ex/ "new_database_schema"). Select anything from the 'Default Collation' dropdown (ex/ "utf8 - utf8_bin"). The 'Schema Name' field will revert back to "new_schema" as soon as the new collation is selected.
[26 Mar 2012 16:25] Valeriy Kravchuk
Thank you for the bug report. Verified on Mac OS X 10.5.6.
[28 Mar 2012 13:41] Valeriy Kravchuk
This is a duplicate of Bug #64259 (looks like all Mac OS X versions are affected).