Description:
cp932(and sjis) is often used for Japanese Windows users.
But that character set includes 0x5c as 2nd bye of kanji character, so it's cause of miss handling strings.
In this case, it affects to view definition.
If I make a view including 0x5c from the client with cp932, view definition is made with additional 0x5c, so it become wrong definition.
How to repeat:
mysql> set names cp932;
Query OK, 0 rows affected (0.00 sec)
mysql> create or replace view v_test
-> as
-> select '十';
Query OK, 0 rows affected (0.05 sec)
mysql> show create table v_test\G
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''十\'
Suggested fix:
No additional 0x5c(\) for escaping for 2nd byte of cp932(sjis) character.
[Work around]
Use UTF-8 client for such a view (e.g. MySQL Workbench for Windows).
Description: cp932(and sjis) is often used for Japanese Windows users. But that character set includes 0x5c as 2nd bye of kanji character, so it's cause of miss handling strings. In this case, it affects to view definition. If I make a view including 0x5c from the client with cp932, view definition is made with additional 0x5c, so it become wrong definition. How to repeat: mysql> set names cp932; Query OK, 0 rows affected (0.00 sec) mysql> create or replace view v_test -> as -> select '十'; Query OK, 0 rows affected (0.05 sec) mysql> show create table v_test\G ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ''十\' Suggested fix: No additional 0x5c(\) for escaping for 2nd byte of cp932(sjis) character. [Work around] Use UTF-8 client for such a view (e.g. MySQL Workbench for Windows).