Bug #31390 | ERROR 1296 (HY000) at line 24: Got error 744 'Character string is invalid | ||
---|---|---|---|
Submitted: | 4 Oct 2007 8:50 | Modified: | 3 Jun 2008 21:56 |
Reporter: | JongSe Park | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S3 (Non-critical) |
Version: | mysql-5.1-telco-7.0 | OS: | Solaris |
Assigned to: | CPU Architecture: | Any | |
Tags: | 'Character string is invalid for given character set', 5.1.22-rc |
[4 Oct 2007 8:50]
JongSe Park
[5 Oct 2007 11:37]
Hartmut Holzgraefe
can you attach the logm_person_meta.sql to this bug or list the contents of the failing line 24? without knowing the actual statement that lead to the error message there isn't much we can do about this bug report ...
[8 Oct 2007 0:29]
JongSe Park
I attached logm_person_meta.sql file
Attachment: logm_person_meta.sql (application/octet-stream, text), 134.74 KiB.
[8 Oct 2007 0:33]
JongSe Park
I think that ndbcluster doesn't support euckr of character set. dosen't it?
[3 Jun 2008 21:56]
Sveta Smirnova
Thank you for the report. Cluster supports euckr. Your file in euckr, but contains statement SET NAMES utf8; So either error or warning is expected. Please read about internalisation at http://dev.mysql.com/doc/refman/5.1/en/internationalization-localization.html But if use memory-based table data is inserted and warning fired. For disk based table error occured. This is not documented inconsistence with disk based tables.