Bug #28463 | 1366 - Incorrect string value | ||
---|---|---|---|
Submitted: | 16 May 2007 7:01 | Modified: | 16 May 2007 7:57 |
Reporter: | Yoon Jay | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | MySQL Server: Errors | Severity: | S2 (Serious) |
Version: | 5.0.37 | OS: | Linux (redhat 3.0) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 1366 - Incorrect string value |
[16 May 2007 7:01]
Yoon Jay
[16 May 2007 7:30]
Sveta Smirnova
Thank you for the report. I can not repeat described behaviour with test probram. For me it looks like not MySQL bug. Please read carefully about character set support at http://dev.mysql.com/doc/refman/5.0/en/charset.html and if you still think this is problem with MySQL and not with the application feel free to reopen the report and provide little program demonstrating described behaviour.
[16 May 2007 7:57]
Yoon Jay
i never got this error message before. today. i change mysql variable and table 1.add unique index Nick_index using btree('Nick') 2.set sql_mode = STRICT_TRANS_TABLES and i find this error at Nick field (varchar(16)) only today! why same query return error or success message? i think it is mysql bug about not english language control. i can't have other idea about this situation. thanks for read.
[17 Oct 2011 4:50]
HungNghiep Tran
I think this problem is a known MySQL's limitation in that it is unable to store 4 byte UTF-8 characters in MySQL before 5.5.3. You can find the latest release here: http://dev.mysql.com/downloads/mysql Note: It is a development release, not a general available release.