Bug #53764 | Creating new Schema defaults to new_schema | ||
---|---|---|---|
Submitted: | 18 May 2010 20:23 | Modified: | 28 May 2010 10:32 |
Reporter: | Bishnu Timalsina | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: SQL Editor | Severity: | S2 (Serious) |
Version: | 5.2.21 RC | OS: | MacOS (10.6.3 64 bit) |
Assigned to: | Alfredo Kojima | CPU Architecture: | Any |
[18 May 2010 20:23]
Bishnu Timalsina
[18 May 2010 20:25]
Bishnu Timalsina
Updated severity to S2
[19 May 2010 5:07]
Susanne Ebrecht
Many thanks for writing a bug report. I am not able to follow you. Do you have a screenshot for us?
[19 May 2010 5:15]
Bishnu Timalsina
Step One
Attachment: step_one.png (image/png, text), 44.67 KiB.
[19 May 2010 5:15]
Bishnu Timalsina
Step Two
Attachment: step_two.png (image/png, text), 126.79 KiB.
[19 May 2010 5:15]
Bishnu Timalsina
Step Three
Attachment: step_three.png (image/png, text), 70.48 KiB.
[19 May 2010 5:16]
Bishnu Timalsina
Step Four
Attachment: step_four.png (image/png, text), 11.21 KiB.
[19 May 2010 5:24]
Bishnu Timalsina
Hi, I've uploaded the screenshots (step 1 to 4) to replicate this bug. Basically I gave a new schema name 'testing' and Default Collation as utf8 and clicked on apply while creating a new schema in schema creating template window. Once I clicked on Apply button, I got this: "CREATE NEW SCHEMA IF NOT EXISTS `new_schema` DEFAULT CHARACTER SET utf8; on step two. As you see the new_schema name should be `testing` but defaults to `new_schema`
[26 May 2010 8:42]
Valeriy Kravchuk
Not repeatable on Windows also. Looks like Mac-specific bug.
[26 May 2010 14:05]
Valeriy Kravchuk
Verified on Mac OS X 10.5.x.
[26 May 2010 14:56]
Alfredo Kojima
Fixed. You can workaround by pressing Return after changing the schema name.
[26 May 2010 17:28]
Johannes Taxacher
fix confirmed in repository
[28 May 2010 10:32]
Tony Bedford
An entry has been added to the 5.2.22 changelog: In the Create Schema dialog of the SQL Editor, when a new schema name was entered, and changes applied, the schema name appeared to revert to the default name new_schema, rather than being changed to the newly specified name. This only happened on Mac OS X.