MySQL Bugs: #31657: MySQL problem with Japanese Character(moji) for enum type.

Bug #31657	MySQL problem with Japanese Character(moji) for enum type.
Submitted:	17 Oct 2007 2:59	Modified:	22 Nov 2007 18:34
Reporter:	Sohel Taslim	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Server: Data Types	Severity:	S3 (Non-critical)
Version:	5	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	It is a problem with Japanese Character.

Description:
I am using utf-8 as default character set for table. 
I can create and alter my table with ENUM data type very well.
In my database table when I try to use Japanese character as ENUM data types value then it generate error.

How to repeat:
ALTER TABLE test_tab CHANGE enum_txt enum_txt ENUM('Text-1','Text-2','Text-3');
↑
Above statement is working without any error.
Error occur for the following statement.
↓
ALTER TABLE test_tab CHANGE enum_txt enum_txt ENUM('Text-1','Text-2','Text-3','日本語');

Can you tell me if I am wrong?

Thank you for a problem report. Please, specify the exact server version, 5.x.y, and send SHOW CREATE TABLE results for the table, as well as the results of:

show variables like 'char%';

Well, my server is →　MySQL 5.0.45

And your asking result as below:

mysql> show create table test_tab;
+----------+--------------+
| Table    | Create Table |
+----------+--------------+
| test_tab  | CREATE TABLE `test_tab` (
  `enum_txt` enum('Text-1','Text-2','“ú?{Œê') character set ujis default NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8|
+----------+--------------+
1 row in set

I got the solution. But the problem was happening when I used MySQL Client Software to create table.

mysql> CREATE TABLE `test_tab` (
  `enum_txt` enum('Text-1','Text-2','日本語') character set ujis default NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8;
Query OK, 0 rows affected

mysql> show create table test_tab;
+--+--+
| Table | Create Table |
+--+--+
| test_tab | CREATE TABLE `test_tab` (
  `enum_txt` enum('Text-1','Text-2','日本語') character set ujis default NULL
) ENGINE=InnoDB DEFAULT CHARSET=utf8 |
+--+--+
1 row in set

Thanks a lot.

Are you tried with the MySQL Query Browser instead of the mysql.exe client?.

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".