Bug #7538 | I can't use extended-ascii character | ||
---|---|---|---|
Submitted: | 27 Dec 2004 7:10 | Modified: | 11 Jan 2005 13:56 |
Reporter: | JANG HONG CHANG | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server | Severity: | S3 (Non-critical) |
Version: | 4.1.8 | OS: | Linux (Linux RedHat 9.0) |
Assigned to: | Alexander Barkov | CPU Architecture: | Any |
[27 Dec 2004 7:10]
JANG HONG CHANG
[28 Dec 2004 20:01]
MySQL Verification Team
Verified with latest 4.1 source tree.
[11 Jan 2005 13:56]
Alexander Barkov
Thank you for taking the time to write to us, but this is not a bug. Please double-check the documentation available at http://www.mysql.com/documentation/ and the instructions on how to report a bug at http://bugs.mysql.com/how-to-report.php Additional info: This is not a bug. The problem is that a single byte with code 138 is not a valid EUC-KR sequence. It is a beginning of a multi-byte sequence. Starting from 4.1, MySQL doesn't allow to write a wrong mylti-byte sequences. Note, a sequence of two bytes with codes 138 is a correct sequence. This query works fine: mysql> insert into t2 (a) values ( concat(char(138),char(138))); Query OK, 1 row affected (0.00 sec) And SELECT does return the value afterwards.