error code 1366 incorrect string value mysql
here for a quick overview of the site Help Center Detailed answers to any questions mysql error 1366 hy000 incorrect string value you might have Meta Discuss the workings and policies of
Mysql Error Code 1366 Incorrect Integer Value
this site About Us Learn more about Stack Overflow the company Business Learn more about hiringSql State Hy000 Error Code 1366 Incorrect String Value
developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow isGeneral Error 1366 Incorrect String Value
a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up MySQL “incorrect string value” error when save unicode string in Django up vote 104 down vote favorite 59 I got strange error message when tried to save first_name, last_name to Django's auth_user incorrect string value for column django model. Failed examples user = User.object.create_user(username, email, password) user.first_name = u'Rytis' user.last_name = u'Slatkevičius' user.save() >>> Incorrect string value: '\xC4\x8Dius' for column 'last_name' at row 104 user.first_name = u'Валерий' user.last_name = u'Богданов' user.save() >>> Incorrect string value: '\xD0\x92\xD0\xB0\xD0\xBB...' for column 'first_name' at row 104 user.first_name = u'Krzysztof' user.last_name = u'Szukiełojć' user.save() >>> Incorrect string value: '\xC5\x82oj\xC4\x87' for column 'last_name' at row 104 Succeed examples user.first_name = u'Marcin' user.last_name = u'Król' user.save() >>> SUCCEED MySQL settings mysql> show variables like 'char%'; +--------------------------+----------------------------+ | Variable_name | Value | +--------------------------+----------------------------+ | character_set_client | utf8 | | character_set_connection | utf8 | | character_set_database | utf8 | | character_set_filesystem | binary | | character_set_results | utf8 | | character_set_server | utf8 | | character_set_system | utf8 | | character_sets_dir | /usr/share/mysql/charsets/ | +--------------------------+----------------------------+ 8 rows in set (0.00 sec) Table charset and collation Table auth_user has utf-8 charset with utf8_general_ci collation. Results of UPDATE command It didn't raise any error when uhere for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of mysql incorrect string value for column at row 1 this site About Us Learn more about Stack Overflow the company Business incorrect string value ' xa0' for column Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask error 1366 (hy000) incorrect string value Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign http://stackoverflow.com/questions/2108824/mysql-incorrect-string-value-error-when-save-unicode-string-in-django up Weird MySQL character set trouble: error number 1366: Incorrect string value up vote 0 down vote favorite I have a PHP script which takes in POST params and saves them to a database. The script itself works fine, but if any of the POST params contains hebrew text, I get the following error: error number 1366: Incorrect string value: '\xF2\xE9\xE3\xE5 \xF7...' for http://stackoverflow.com/questions/20503223/weird-mysql-character-set-trouble-error-number-1366-incorrect-string-value column 'Name' at row 1 The column definition is: `Name` varchar(255) CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL, The table and the database are also defined as CHARACTER SET utf8 COLLATE utf8_general_ci. Also, stripslashes is executed on the query before it is run. The curious thing is that the original column definition did not include CHARACTER SET and COLLATE. When it didn't have those, running the same insert statement with hebrew characters through MySQL Workbench got me the same error - but only as a warning. Then I added the CHARACTER SET and COLLATE params to the column definitions, rebuilt the table and ran my queries again though Workbench - all good. ... but the PHP script still returns this error. Does anyone know why this is happening? Can I suppress warnings in the SQL statement itself so as just to ignore these? EDIT: PHP code: function dbConnect() { global $host, $user, $pwd, $db, $MYSQL_ERRNO, $MYSQL_ERROR; $dbConn = mysql_connect($host,$user,$pwd); if (!$dbConn) { $MYSQL_ERRNO = 0; $MYSQL_ERROR = "Could not connect to $host"; return false; } else if ($db && !mysql_select_db($db)) { $MYSQL_ERRNO = mysql_errno(); $MYSQL_ERROR = mysql_
Community Podcasts MySQL.com Downloads Documentation Section Menu: MySQL Forums :: Character Sets, Collation, Unicode :: ERROR 1366 (HY000): http://forums.mysql.com/read.php?103,418508,418508 Incorrect string value: '\x9B' New Topic Advanced Search ERROR 1366 (HY000): Incorrect string value: '\x9B' Posted by: T Vadla () Date: May 03, 2011 07:12AM In http://languor.us/mysql-encoding-error-warning-code-1366-incorrect-string-value-xe9 my MySQL-database I get an 1366 error when I try to insert the letter 'ø'. I have made everything in my database utf8, so I incorrect string thought this should do it. Can anyone tell me what's wrong? This is how I make the database: CREATE DATABASE IF NOT EXISTS foodbase_2 CHARACTER SET utf8 COLLATE utf8_general_ci; USE foodbase_2; CREATE TABLE IF NOT EXISTS User ( UserId int(4) NOT NULL auto_increment, Username varchar(15) NOT NULL, Password varchar(15) NOT NULL, incorrect string value Firstname varchar(25) NOT NULL, Lastname varchar(30) NOT NULL, PRIMARY KEY (UserId), UNIQUE KEY (Username) ) ENGINE=INNODB; mysql> set names utf8; When I try to insert a row through the command shell in Windows I get the following message: mysql> insert into user values('0000', 'a', 'a', 'a', 'ø'); ERROR 1366 (HY000): Incorrect string value: '\x9B' for column 'Lastname' at row 1 mysql> select lastname, hex(lastname), char(lastname), char_length(lastname) from user; +----------+---------------+----------------+-----------------------+ | lastname | hex(lastname) | char(lastname) | char_length(lastname) | +----------+---------------+----------------+-----------------------+ | a | 61 | | 1 | +----------+---------------+----------------+-----------------------+ mysql> show VARIABLES LIKE '%CHAR%'; --------------------------+--------- Variable_name | Value --------------------------+--------- character_set_client | utf8 character_set_connection | utf8 character_set_database | utf8 character_set_filesystem | binary character_set_results | utf8 character_set_server | utf8 character_set_system | utf8 character_sets_dir | C:\Progr... mysql> show VARIABLES LIKE '%Coll%'; +----------------------+-----------------+ | Variable_name | Value | +----------------------+-----------------+ | collation_connection | utf8_general_ci | | collation_database | utf8_general_ci | | collation_server | utf8_general_ci | +----------------------+-----------------+ Navigate:Previous Message•Nex
on Sun, 2013-06-02 13:10 While performing a CSV import recently, I ran into the following error messages: Warning (Code 1366): Incorrect string value: '\xE9, a <...' for column 'body' at row 3
Warning (Code 1366): Incorrect string value: '\xE6. He ...' for column 'body' at row 24
Warning (Code 1366): Incorrect string value: '\xE9, and...' for column 'body' at row 26 The first message was triggered due to the accented é in the word, protegé, in the input. The rest of the field was not imported. The others were similarly triggered. The problem here is the mixing and matching of encodings that can happen during imports. While I am usually quite anal to have everything in UTF-8 during imports/exports, I appear to have missed a spot, which, in this case, was the encoding of the CSV file. I confirmed this by finding out information on the file which gave me: bad.csv: ISO-8859 English text, with very long lines, with CRLF line terminators Once I used Vim to change the encoding of the file to UTF-8, this changed to: good.csv: UTF-8 Unicode English text, with very long lines, with CRLF line terminators A Windows trick is to open the text file in Notepad and save it as a new UTF-8 file via File -> Save As. Once this change was made, my import went through swimmingly. Tags: mysqlVimLinuxWindowsEncoding Add new comment Similar content Setting up Unicode support for PuTTY Changing the charset/encoding of a file in Linux Changing a file's encoding using Vim MySQL charset issues while importing data using LOAD DATA INFILE sed: Deleting all lines between two types of lines Configuring Vim/Gvim to use spaces instead of TABs for indentation Vim/Gvim and missing line numbers in the interface PDOException: SQLSTATE[HY000]: General error: 144 Table 'cache_menu' is marked as crashed and last (automatic?) repair failed: DELETE FROM {cache_menu}; (Windows) Gvim: Backspace in insert mode does not delete text Edimax EW-7316Ug Wireless 11b/g adapter and Linux All times are UTC. All content licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0 License.