Bug #10217 The SHOW CREATE TABLE command is corrupting Unicode table and column names
Submitted: 27 Apr 2005 21:15 Modified: 23 Jan 2006 22:48
Reporter: David Christian Email Updates:
Status: Can't repeat Impact on me:
None 
Category:Connector / NET Severity:S2 (Serious)
Version:5.0.4 OS:Windows (Windows XP SP2)
Assigned to: CPU Architecture:Any

[27 Apr 2005 21:15] David Christian
Description:
The SHOW CREATE TABLE command is not properly representing unicode table and column names.  Conversly, the DESCRIBE command is working just fine.

How to repeat:
Create a table with Japanese table and/or column names.
Use SHOW CREATE TABLE table to view the script (corrupted).
Use DESCRIBE table to view the columns (display fine).
[27 Apr 2005 21:15] David Christian
Screenshot demonstrating corruption

Attachment: CreateTableCorruption.PNG (image/x-png, text), 58.83 KiB.

[7 May 2005 12:44] Hartmut Holzgraefe
Can you please provide us with an example CREATE statement for this?
[9 May 2005 17:01] David Christian
Table with Japanese name and column names

Attachment: JapaneseTable.sql (text/plain), 276 bytes.

[7 Jun 2005 23:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
[7 Jun 2005 23:12] David Christian
I DID give you feedback.  I supplied both an example Unicode script with the CREATE TABLE statement and a screenshot - please look at the attached files.
[27 Jun 2005 5:42] Aleksey Kishkin
Hi! tested it against 5.0.7-nt on win xp sp2 and was not able to reproduce. Please look at attached screenshoot.

Could you check 5.0.7 version (instead of 5.0.4)?
[27 Jun 2005 5:43] Aleksey Kishkin
screenshoot of 'create table' with utf8 tablename

Attachment: bug10217.JPG (image/jpeg, text), 74.49 KiB.

[23 Jan 2006 22:48] David Christian
This bug appears to be in the Connector/Net.  This is a duplicate of another bug report I created 16588.  There are detailed steps on how to replicate the issue there.