Bug #64259 | Improper reset of Schema Name field in SQL Editor | ||
---|---|---|---|
Submitted: | 8 Feb 2012 1:14 | Modified: | 23 Jul 2012 23:17 |
Reporter: | Anthony Stramer | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S3 (Non-critical) |
Version: | 5.2.37, 5.2.38 | OS: | MacOS (10.5.6, 10.7.2) |
Assigned to: | CPU Architecture: | Any | |
Tags: | collation, create, DEFAULT, editor, reset, schema, SQL |
[8 Feb 2012 1:14]
Anthony Stramer
[8 Feb 2012 1:34]
MySQL Verification Team
Not repeatable on Windows.
[8 Feb 2012 4:58]
Valeriy Kravchuk
I can not repeat this on Mac OS X 10.5.6.
[27 Feb 2012 9:57]
Valeriy Kravchuk
Please, check if the same problem still happens in your environment with a newer version, 5.2.38.
[27 Feb 2012 10:36]
Anthony Stramer
Yes the issue is still present in 5.2.38. Also I am running OS X 10.7.2.
[1 Mar 2012 14:53]
Johannes Taxacher
verified on 10.7 (apparently lion specific)
[28 Mar 2012 13:43]
Valeriy Kravchuk
Bug #64764 and Bug #64787 were marked as duplicates of this one.
[2 Apr 2012 13:18]
Valeriy Kravchuk
Bug #64840 was marked as a duplicate of this one.
[14 Jun 2012 3:37]
Alfredo Kojima
As a workaround, press Return after renaming the schema.
[23 Jul 2012 23:17]
Philip Olson
This has been fixed as of the soon-to-be-released Workbench 5.2.41, and here's the changelog entry: Changing the "Default Collation" of a schema after changing its name would reset the schema name to "new_schema".