blocks|key|336398|text|"\xE4\xC5\xCC\xC9\xD3\xD8"不是有效的UTF-8。使用Python测试：|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|336399|>>>+"\xE4\xC5\xCC\xC9\xD3\xD8".decode("utf-8")
...
UnicodeDecodeError:+'utf8'+codec+can't+decode+bytes+in+position+0-2:+invalid+data|code-block|syntax|javascript|336400|如果您正在寻找一种方法来避免数据库中的解码错误，那么cp1252编码(也就是“Windows1252”，也就是"Windows+Western+European")是最宽松的编码方式--每个字节值都是一个有效的代码点。|336401|当然，它不会再理解真正的UTF-8，也不会理解任何其他非cp1252编码，但听起来您并不太关心这一点？|336402|entityMap^0|0|Q|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|T|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

<code>"\xE4\xC5\xCC\xC9\xD3\xD8"</code> isn't valid UTF-8. Tested using Python:

<pre><code>&gt;&gt;&gt; "\xE4\xC5\xCC\xC9\xD3\xD8".decode("utf-8")
...
UnicodeDecodeError: 'utf8' codec can't decode bytes in position 0-2: invalid data
</code></pre>

If you're looking for a way to avoid decoding errors within the database, the cp1252 encoding (aka "Windows-1252" aka "Windows Western European") is the most permissive encoding there is - every byte value is a valid code point.

Of course it's not going to understand genuine UTF-8 any more, nor any other non-cp1252 encoding, but it sounds like you're not too concerned about that?

blocks|key|3313380|text|当我遇到这个不正确的字符串值：'\xF8‘时，对于使用scriptcase的列错误，我的解决方案是确保我的数据库设置为utf8常规ci，我的字段排序也是如此。然后，当我做我的数据导入的csv文件，我加载csv到UE工作室，然后保存为utf8格式和哇啦！它就像一个护身符，29000条记录都没有错误。之前，我试图导入一个excel创建的csv。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3313381|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

The solution for me when running into this Incorrect string value: '\xF8' for column error using scriptcase was to be sure that my database is set up for utf8 general ci and so are my field collations. Then when I do my data import of a csv file I load the csv into UE Studio then save it formatted as utf8 and Voila! It works like a charm, 29000 records in there no errors. Previously I was trying to import an excel created csv.

blocks|key|3100609|text|将更新为以下答案：|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3100610|当这个问题被问到的时候，MySQL中的"UTF8“指的是utf8mb3。在此期间，添加了utf8mb4，但据我所知，MySQL+"UTF8“并未切换为utf8mb4。|CODE|3100611|这意味着，如果你是认真的，你需要特别写上"utf8mb4“(并且你应该使用utf8mb4)。|3100612|我将把这个放在这里，而不是仅仅编辑答案，以明确说"UTF8“时仍然有区别。|3100613|原始|3100614|我不建议Richies回答，因为您正在搞乱数据库中的数据。你不会修复你的问题，而是试图“隐藏”它，并且不能对废弃的数据执行必要的数据库操作。|3100615|如果遇到此错误，您发送的数据不是UTF-8编码的，或者您的连接不是UTF-8编码的。首先，验证数据源(文件，...)实际上是UTF-8。|3100616|然后，检查您的数据库连接，连接后应执行以下操作：|3100617|SET+NAMES+'utf8mb4';
SET+CHARACTER+SET+utf8mb4;|code-block|syntax|javascript|3100618|接下来，验证存储数据的表是否具有utf8mb4字符集：|3100619|SELECT
++`tables`.`TABLE_NAME`,
++`collations`.`character_set_name`
FROM
++`information_schema`.`TABLES`+AS+`tables`,
++`information_schema`.`COLLATION_CHARACTER_SET_APPLICABILITY`+AS+`collations`
WHERE
++`tables`.`table_schema`+=+DATABASE()
++AND+`collations`.`collation_name`+=+`tables`.`table_collation`
;|3100620|最后，检查您的数据库设置：|3100621|mysql>+show+variables+like+'%25colla%25';
mysql>+show+variables+like+'%25charac%25';|3100622|如果源、传输和目标都是utf8mb4，那么问题就解决了；)|3100623|entityMap^0|0|1|0|S|7|18|7|23|7|0|11|7|0|0|0|2|0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@$9|1C|A|1D|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|1E|8|@$9|1F|A|1G|B|H]|$9|1H|A|1I|B|H]|$9|1J|A|1K|B|H]]|D|@]|E|$]]|$1|I|3|J|5|6|7|1L|8|@$9|1M|A|1N|B|H]]|D|@]|E|$]]|$1|K|3|L|5|6|7|1O|8|@]|D|@]|E|$]]|$1|M|3|N|5|6|7|1P|8|@$9|1Q|A|1R|B|C]]|D|@]|E|$]]|$1|O|3|P|5|6|7|1S|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|1T|8|@]|D|@]|E|$]]|$1|S|3|T|5|6|7|1U|8|@]|D|@]|E|$]]|$1|U|3|V|5|W|7|1V|8|@]|D|@]|E|$X|Y]]|$1|Z|3|10|5|6|7|1W|8|@]|D|@]|E|$]]|$1|11|3|12|5|W|7|1X|8|@]|D|@]|E|$X|Y]]|$1|13|3|14|5|6|7|1Y|8|@]|D|@]|E|$]]|$1|15|3|16|5|W|7|1Z|8|@]|D|@]|E|$X|Y]]|$1|17|3|18|5|6|7|20|8|@]|D|@]|E|$]]|$1|19|3|-4|5|6|7|21|8|@]|D|@]|E|$]]]|1A|$]]

UPDATE to the below answer:
The time the question was asked, &quot;UTF8&quot; in MySQL meant <code>utf8mb3</code>. In the meantime, <code>utf8mb4</code> was added, but to my knowledge MySQLs &quot;UTF8&quot; was not switched to mean <code>utf8mb4</code>.
That means, you'd need to specifically put &quot;utf8mb4&quot;, if you mean it (and you should use <code>utf8mb4</code>)
I'll keep this here instead of just editing the answer, to make clear there is still a difference when saying &quot;UTF8&quot;
Original
I would not suggest Richies answer, because you are screwing up the data inside the database. You would not fix your problem but try to &quot;hide&quot; it and not being able to perform essential database operations with the crapped data.
If you encounter this error either the data you are sending is not UTF-8 encoded, or your connection is not UTF-8. First, verify, that the data source (a file, ...) really is UTF-8.
Then, check your database connection, you should do this after connecting:
<pre><code>SET NAMES 'utf8mb4';
SET CHARACTER SET utf8mb4;
</code></pre>
Next, verify that the tables where the data is stored have the utf8mb4 character set:
<pre><code>SELECT
 `tables`.`TABLE_NAME`,
 `collations`.`character_set_name`
FROM
 `information_schema`.`TABLES` AS `tables`,
 `information_schema`.`COLLATION_CHARACTER_SET_APPLICABILITY` AS `collations`
WHERE
 `tables`.`table_schema` = DATABASE()
 AND `collations`.`collation_name` = `tables`.`table_collation`
;
</code></pre>
Last, check your database settings:
<pre><code>mysql&gt; show variables like '%colla%';
mysql&gt; show variables like '%charac%';
</code></pre>
If source, transport and destination are utf8mb4, your problem is gone;)

blocks|key|336450|text|通常，当您向编码/排序规则不兼容的列中插入字符串时，就会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|336451|当我有触发器时，我得到了这个错误，由于某种原因，它继承了服务器的排序规则。mysql的默认值是(至少在Ubuntu上是)带有瑞典语排序规则的拉丁文-1。尽管我已经将数据库和所有表设置为UTF-8，但我还没有设置my.cnf|offset|length|style|CODE|336452|/etc/mysql/my.cnf：|336453|[mysqld]
character-set-server=utf8
default-character-set=utf8|code-block|syntax|javascript|336454|并且必须列出使用utf8-*的所有触发器|336455|select+TRIGGER_SCHEMA,+TRIGGER_NAME,+CHARACTER_SET_CLIENT,+COLLATION_CONNECTION,+DATABASE_COLLATION+from+information_schema.TRIGGERS|336456|这里列出的一些变量也应该使用utf-8-*+(没有拉丁语-1或其他编码)：|336457|show+variables+like+'char%25';|336458|entityMap^0|0|2X|6|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|L|7|15|8|@]|9|@]|A|$M|N]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|V|5|L|7|17|8|@]|9|@]|A|$M|N]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

In general, this happens when you insert strings to columns with incompatible encoding/collation.

I got this error when I had TRIGGERs, which inherit server's collation for some reason. 
And mysql's default is (at least on Ubuntu) latin-1 with swedish collation.
Even though I had database and all tables set to UTF-8, I had yet to set <code>my.cnf</code>:

/etc/mysql/my.cnf :

<pre><code>[mysqld]
character-set-server=utf8
default-character-set=utf8
</code></pre>

And this must list all triggers with utf8-*:

<pre><code>select TRIGGER_SCHEMA, TRIGGER_NAME, CHARACTER_SET_CLIENT, COLLATION_CONNECTION, DATABASE_COLLATION from information_schema.TRIGGERS
</code></pre>

And some of variables listed by this should also have utf-8-* (no latin-1 or other encoding):

<pre><code>show variables like 'char%';
</code></pre>

blocks|key|336477|text|我今天解决了这个问题，将列改为'LONGBLOB‘类型，它存储原始字节而不是UTF-8字符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|336478|这样做的唯一缺点是您必须自己处理编码。如果您的应用程序的一个客户端使用UTF-8编码，而另一个客户端使用CP1252，您的电子邮件可能会发送错误的字符。为了避免这种情况，总是在所有的应用程序中使用相同的编码(例如UTF-8)。|offset|length|style|BOLD|336479|有关TEXT/LONGTEXT和BLOB/LONGBLOB之间差异的更多详细信息，请参阅本页http://dev.mysql.com/doc/refman/5.0/en/blob.html。在网络上也有很多关于这两个问题的讨论。|336480|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.0/en/blob.html^0|0|2D|A|0|1A|1C|0|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@$D|W|E|X|1|Y]]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]]]

I solved this problem today by altering the column to 'LONGBLOB' type which stores raw bytes instead of UTF-8 characters.

The only disadvantage of doing this is that you have to take care of the encoding yourself. If one client of your application uses UTF-8 encoding and another uses CP1252, you may have your emails sent with incorrect characters. To avoid this, always use the same encoding (e.g. UTF-8) across all your applications.

Refer to this page <a href="http://dev.mysql.com/doc/refman/5.0/en/blob.html" rel="noreferrer">http://dev.mysql.com/doc/refman/5.0/en/blob.html</a> for more details of the differences between TEXT/LONGTEXT and BLOB/LONGBLOB. There are also many other arguments on the web discussing these two.

blocks|key|3313591|text|我已经尝试了上面所有的解决方案(它们都带来了有效的观点)，但对我来说都不起作用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3313592|直到我发现我的MySQL表字段映射在C#中使用了不正确的类型：MySqlDbType.Blob。我将其更改为MySqlDbType.Text，现在我可以编写所有我想要的UTF8符号！|offset|length|style|BOLD|3313593|附注：我的MySQL表字段是LongText类型的。但是，当我使用MyGeneration软件自动生成字段映射时，它会自动在C#中将字段类型设置为MySqlDbType.Blob。|3313594|有趣的是，我使用带有UTF8字符的MySqlDbType.Blob类型已经有好几个月了，没有遇到任何问题，直到有一天我试着写一个包含一些特定字符的字符串。|3313595|希望这对正在努力寻找错误原因的人有所帮助。|3313596|entityMap^0|0|V|G|1I|G|0|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|V|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|W|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|X|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|O|$]]

I have tried all of the above solutions (which all bring valid points), but nothing was working for me. 

Until I found that my MySQL table field mappings in C# was using an incorrect type: MySqlDbType.Blob . I changed it to MySqlDbType.Text and now I can write all the UTF8 symbols I want! 

p.s. My MySQL table field is of the "LongText" type. However, when I autogenerated the field mappings using MyGeneration software, it automatically set the field type as MySqlDbType.Blob in C#. 

Interestingly, I have been using the MySqlDbType.Blob type with UTF8 characters for many months with no trouble, until one day I tried writing a string with some specific characters in it.

Hope this helps someone who is struggling to find a reason for the error.

blocks|key|335466|text|该错误意味着您的字符串具有错误的编码(例如，您正在尝试将ISO-8859-1编码的字符串输入到UTF-8编码列)，或者该列不支持您尝试输入的数据。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|335467|在实践中，后一个问题是由UTF+8实现引起的，当以MySQL+-8表示时，它只支持需要1-3个字节的UNICODE字符。详情请参见"Incorrect+string+value"+when+trying+to+insert+UTF-8+into+MySQL+via+JDBC?。诀窍是使用列类型UTF-8而不是utf8类型，尽管名称如此，但实际上并不支持所有的utf8mb4+-8。前一种类型是用于所有UTF-8字符串的正确类型。|offset|length|style|CODE|335468|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/10957238/incorrect-string-value-when-trying-to-insert-utf-8-into-mysql-via-jdbc^0|0|4B|4|50|7|1T|21|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@$D|V|E|W|1|X]]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

That error means that either you have the string with incorrect encoding (e.g. you're trying to enter ISO-8859-1 encoded string into UTF-8 encoded column), or the column does not support the data you're trying to enter.
In practice, the latter problem is caused by MySQL UTF-8 implementation that only supports UNICODE characters that need 1-3 bytes when represented in UTF-8. See <a href="https://stackoverflow.com/questions/10957238/incorrect-string-value-when-trying-to-insert-utf-8-into-mysql-via-jdbc">&quot;Incorrect string value&quot; when trying to insert UTF-8 into MySQL via JDBC?</a> for details. The trick is to use column type <code>utf8mb4</code> instead of type <code>utf8</code> which doesn't actually support all of UTF-8 despite the name. The former type is the correct type to use for all UTF-8 strings.

blocks|key|334031|text|MySQL的utf-8类型实际上不是正确的utf-8+-它只使用每个字符最多三个字节，并且只支持基本的多语言平面(即没有Emoji，没有astral平面等)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334032|如果需要存储来自更高Unicode平面的值，则需要utf8mb4+encodings。|offset|length|334033|entityMap|0|LINK|mutability|MUTABLE|url|http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html^0|0|P|H|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

MySQL’s utf-8 types are not actually proper utf-8 – it only uses up to three bytes per character and supports only the Basic Multilingual Plane (i.e. no Emoji, no astral plane, etc.).

If you need to store values from higher Unicode planes, you need the <a href="http://dev.mysql.com/doc/refman/5.5/en/charset-unicode-utf8mb4.html">utf8mb4 encodings</a>.

blocks|key|3313711|text|我在列名之前添加了binary，并解决了字符集错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3313712|插入tableA值(二进制stringcolname1)；|3313713|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I added binary before the column name and solve the charset error.

insert into tableA values(binary stringcolname1);

blocks|key|334058|text|对我来说，首先我遇到了一个‘？’在我的网站上，然后我检查了Mysql的字符集，它现在是拉丁语，所以我把它改成utf-8，然后我重新启动我的项目，然后我得到了与你相同的错误，然后我发现我忘了改变数据库的字符集，改成utf-8，突然，它起作用了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334059|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case ,first i've meet a '???' in my website, then i check Mysql's character set which is latin now ,so i change it into utf-8,then i restart my project ,then i got the same error with you , then i found that i forget to change the database's charset and change into utf-8, boom,it worked.

blocks|key|3100951|text|首先检查您的default_character_set_name是否为utf8。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3100952|SELECT+default_character_set_name+FROM+information_schema.SCHEMATA+S+WHERE+schema_name+=+"DBNAME";|code-block|syntax|javascript|3100953|如果结果不是utf8，则必须转换数据库。首先，您必须保存一个转储。|3100954|要将指定数据库中所有表的字符集编码更改为UTF-8，请在命令行中键入以下命令。将DBNAME替换为数据库名称：|3100955|mysql+--database=DBNAME+-B+-N+-e+"SHOW+TABLES"+%7C+awk+'{print+"SET+foreign_key_checks+=+0;+ALTER+TABLE",+$1,+"CONVERT+TO+CHARACTER+SET+utf8+COLLATE+utf8_general_ci;+SET+foreign_key_checks+=+1;+"}'+%7C+mysql+--database=DBNAME|3100956|要将数据库本身的字符集编码更改为UTF8，请在mysql>提示符下输入以下命令。将DBNAME替换为数据库名称：|offset|length|style|BOLD|3100957|ALTER+DATABASE+DBNAME+CHARACTER+SET+utf8+COLLATE+utf8_general_ci;|3100958|您现在可以重试将utf8字符写入数据库。当我尝试将200000行csv文件上传到我的数据库中时，此解决方案可以帮助我。|3100959|entityMap^0|0|0|0|0|0|N|5|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|12|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|13|8|@$O|14|P|15|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|U|3|V|5|6|7|17|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|18|8|@]|9|@]|A|$]]]|X|$]]

First check if your default_character_set_name is utf8.

<pre><code>SELECT default_character_set_name FROM information_schema.SCHEMATA S WHERE schema_name = "DBNAME";
</code></pre>

If the result is not utf8 you must convert your database. At first you must save a dump.

To change the character set encoding to UTF-8 for all of the tables in the specified database, type the following command at the command line. Replace DBNAME with the database name:

<pre class="lang-sh prettyprint-override"><code>mysql --database=DBNAME -B -N -e "SHOW TABLES" | awk '{print "SET foreign_key_checks = 0; ALTER TABLE", $1, "CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci; SET foreign_key_checks = 1; "}' | mysql --database=DBNAME
</code></pre>

To change the character set encoding to UTF-8 for the database itself, type the following command at the mysql> prompt. Replace DBNAME with the database name:

<pre><code>ALTER DATABASE DBNAME CHARACTER SET utf8 COLLATE utf8_general_ci;
</code></pre>

You can now retry to to write utf8 character into your database. This solution help me when i try to upload 200000 row of csv file into my database.

blocks|key|3313795|text|尽管您的排序规则设置为utf8_general_ci，但我怀疑数据库、表甚至列的字符编码可能不同。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3313796|ALTER+TABLE+tabale_name+MODIFY+COLUMN+column_name+VARCHAR(255)++
CHARACTER+SET+utf8+COLLATE+utf8_general_ci+NOT+NULL;|code-block|syntax|javascript|3313797|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Although your collation is set to utf8_general_ci, I suspect that the character encoding of the database, table or even column may be different. 

<pre><code>ALTER TABLE tabale_name MODIFY COLUMN column_name VARCHAR(255) 
CHARACTER SET utf8 COLLATE utf8_general_ci NOT NULL;
</code></pre>

blocks|key|3101043|text|我得到了一个类似的错误(Incorrect+string+value:+'\xD0\xBE\xDO\xB2.+...'+for+'content'+at+row+1)。我尝试将column的字符集更改为utf8mb4，然后错误更改为'Data+too+long+for+column+'content'+at+row+1'。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3101044|事实证明，mysql显示了错误的错误。我将列的字符集恢复为utf8，并将列的类型更改为MEDIUMTEXT。在那之后，错误消失了。|3101045|我希望它能帮助一些人。|3101046|顺便说一句，MariaDB在相同的情况下(我在那里测试了相同的插入)只需要剪切文本而不会出错。|3101047|entityMap^0|C|1Y|2T|7|38|19|0|T|4|17|A|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|U|8|@$9|V|A|W|B|C]|$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|Z|8|@]|D|@]|E|$]]|$1|J|3|K|5|6|7|10|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|M|$]]

I got a similar error (<code>Incorrect string value: '\xD0\xBE\xDO\xB2. ...' for 'content' at row 1</code>). I have tried to change character set of column to <code>utf8mb4</code> and after that the error has changed to <code>'Data too long for column 'content' at row 1'</code>. 
It turned out that mysql shows me wrong error. I turned back character set of column to <code>utf8</code> and changed type of the column to <code>MEDIUMTEXT</code>. After that the error disappeared. 
I hope it helps someone. 
By the way MariaDB in same case (I have tested the same INSERT there) just cut a text without error.

blocks|key|3313868|text|表和字段具有错误的编码；但是，您可以将它们转换为UTF-8。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3313869|ALTER+TABLE+logtest+CONVERT+TO+CHARACTER+SET+utf8+COLLATE+utf8_general_ci;

ALTER+TABLE+logtest+DEFAULT+CHARACTER+SET+utf8+COLLATE+utf8_general_ci;

ALTER+TABLE+logtest+CHANGE+title+title+VARCHAR(100)+CHARACTER+SET+utf8+COLLATE+utf8_general_ci;|code-block|syntax|javascript|3313870|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

The table and fields have the wrong encoding; however, you can convert them to UTF-8.

<pre><code>ALTER TABLE logtest CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;

ALTER TABLE logtest DEFAULT CHARACTER SET utf8 COLLATE utf8_general_ci;

ALTER TABLE logtest CHANGE title title VARCHAR(100) CHARACTER SET utf8 COLLATE utf8_general_ci;
</code></pre>

blocks|key|334123|text|您好，我也得到了这个错误，当我使用我的在线数据库从谷歌爸爸服务器，我认为它有mysql版本的5.1或更高。但是当我在我的本地主机服务器(5.7版)上创建这个表并使用mysql+yog复制到在线服务器上时，我觉得问题出在字符集上|type|unstyled|depth|inlineStyleRanges|entityRanges|data|334124|Screenshot+Here|offset|length|334125|entityMap|0|LINK|mutability|MUTABLE|url|https://i.stack.imgur.com/5JC3u.jpg^0|0|0|F|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

Hi i also got this error when i use my online databases from godaddy server
i think it has the mysql version of 5.1 or more. but when i do from my localhost server (version 5.7) it was fine after that i created the table from local server and copied to the online server using mysql yog i think the problem is with character set

<a href="https://i.stack.imgur.com/5JC3u.jpg" rel="nofollow noreferrer">Screenshot Here</a>

blocks|key|3313942|text|1-你必须在你的连接中声明编码UTF8的属性。http://php.net/manual/en/mysqli.set-charset.php。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3313943|2-如果您使用mysql命令行来执行脚本，则必须使用标志，如：Cmd:+C:\wamp64\bin\mysql\mysql5.7.14\bin\mysql.exe++-h+localhost+-u+root++-P+3306+++--default-character-set=utf8+omega_empresa_parametros_336+<+C:\wamp64\www\PontoEletronico\PE10002Corporacao\BancoDeDadosModelo\omega_empresa_parametros.sql|style|CODE|3313944|entityMap|0|LINK|mutability|MUTABLE|url|http://php.net/manual/en/mysqli.set-charset.php^0|N|1B|0|0|V|6N|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@$A|Q|B|R|1|S]]|C|$]]|$1|D|3|E|5|6|7|T|8|@$A|U|B|V|F|G]]|9|@]|C|$]]|$1|H|3|-4|5|6|7|W|8|@]|9|@]|C|$]]]|I|$J|$5|K|L|M|C|$N|O]]]]

1 - You have to declare in your connection the propertie of enconding UTF8. <a href="http://php.net/manual/en/mysqli.set-charset.php" rel="nofollow noreferrer">http://php.net/manual/en/mysqli.set-charset.php</a>.

2 - If you are using mysql commando line to execute a script, you have to use the flag, like:
<code>Cmd: C:\wamp64\bin\mysql\mysql5.7.14\bin\mysql.exe -h localhost -u root -P 3306 --default-character-set=utf8 omega_empresa_parametros_336 &lt; C:\wamp64\www\PontoEletronico\PE10002Corporacao\BancoDeDadosModelo\omega_empresa_parametros.sql</code>

blocks|key|3101120|text|为了修复这个错误，我通过遵循this+detailed+tutorial将我的MySQL数据库升级到了utf8mb4，它支持完整的Unicode字符集。我建议仔细阅读它，因为有相当多的陷阱(例如，由于新的编码，索引键可能会变得太大，之后您必须修改字段类型)。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3101121|entityMap|0|LINK|mutability|MUTABLE|url|https://mathiasbynens.be/notes/mysql-utf8mb4^0|E|M|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

To fix this error I upgraded my MySQL database to utf8mb4 which supports the full Unicode character set by following <a href="https://mathiasbynens.be/notes/mysql-utf8mb4" rel="nofollow noreferrer">this detailed tutorial</a>. I suggest going through it carefully, because there are quite a few gotchas (e.g. the index keys can become too large due to the new encodings after which you have to modify field types).

blocks|key|3313978|text|这里有很好的答案。我只是添加了我的，因为我遇到了相同的错误，但它被证明是一个完全不同的问题。(表面上可能是相同的，但根本原因不同。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3313979|对于我来说，以下字段发生了错误：|3313980|@Column(nullable+=+false,+columnDefinition+=+"VARCHAR(255)")
private+URI+consulUri;|code-block|syntax|javascript|3313981|这最终作为URI类的二进制序列化存储在数据库中。这没有在单元测试(使用H2)或CI/集成测试(使用MariaDB4j)中引发任何标志，它在我们的类似生产的设置中失败了。(不过，一旦理解了问题，就很容易在MariaDB4j实例中看到错误的值；它只是不会破坏测试。)解决方案是构建一个自定义类型映射器：|offset|length|style|CODE|3313982|package+redacted;

import+javax.persistence.AttributeConverter;
import+java.net.URI;
import+java.net.URISyntaxException;

import+static+java.lang.String.format;

public+class+UriConverter+implements+AttributeConverter<URI,+String>+{
++++@Override
++++public+String+convertToDatabaseColumn(URI+attribute)+{
++++++++return+attribute.toString();
++++}

++++@Override
++++public+URI+convertToEntityAttribute(String+field)+{
++++++++try+{
++++++++++++return+new+URI(field);
++++++++}
++++++++catch+(URISyntaxException+e)+{
++++++++++++throw+new+RuntimeException(format("could+not+convert+database+field+to+URI:+%25s",+field));
++++++++}
++++}
}|3313983|使用方法如下：|3313984|@Column(nullable+=+false,+columnDefinition+=+"VARCHAR(255)")
@Convert(converter+=+UriConverter.class)
private+URI+consulUri;|3313985|就Hibernate而言，它似乎有一堆provided+type+mappers，包括用于java.net.URL的，但没有用于java.net.URI的(这正是我们这里需要的)。|3313986|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/vorburger/MariaDB4j|1|https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/types.html#types-value-basic^0|0|0|0|5|3|1D|9|0|0|0|0|0|19|C|1S|C|J|L|1|0^^$0|@$1|2|3|4|5|6|7|16|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|17|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|18|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|19|8|@$K|1A|L|1B|M|N]]|9|@$K|1C|L|1D|1|1E]]|A|$]]|$1|O|3|P|5|F|7|1F|8|@]|9|@]|A|$G|H]]|$1|Q|3|R|5|6|7|1G|8|@]|9|@]|A|$]]|$1|S|3|T|5|F|7|1H|8|@]|9|@]|A|$G|H]]|$1|U|3|V|5|6|7|1I|8|@$K|1J|L|1K|M|N]|$K|1L|L|1M|M|N]]|9|@$K|1N|L|1O|1|1P]]|A|$]]|$1|W|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|15]]]]

There's good answers in here. I'm just adding mine since I ran into the same error but it turned out to be a completely different problem. (Maybe on the surface the same, but a different root cause.)

For me the error happened for the following field:

<pre><code>@Column(nullable = false, columnDefinition = "VARCHAR(255)")
private URI consulUri;
</code></pre>

This ends up being stored in the database as a binary serialization of the <code>URI</code> class. This didn't raise any flags with unit testing (using H2) or CI/integration testing (using <a href="https://github.com/vorburger/MariaDB4j" rel="nofollow noreferrer">MariaDB4j</a>), it blew up in our production-like setup. (Though, once the problem was understood, it was easy enough to see the wrong value in the MariaDB4j instance; it just didn't blow up the test.) The solution was to build a custom type mapper:

<pre><code>package redacted;

import javax.persistence.AttributeConverter;
import java.net.URI;
import java.net.URISyntaxException;

import static java.lang.String.format;

public class UriConverter implements AttributeConverter&lt;URI, String&gt; {
 @Override
 public String convertToDatabaseColumn(URI attribute) {
 return attribute.toString();
 }

 @Override
 public URI convertToEntityAttribute(String field) {
 try {
 return new URI(field);
 }
 catch (URISyntaxException e) {
 throw new RuntimeException(format("could not convert database field to URI: %s", field));
 }
 }
}
</code></pre>

Used as follows:

<pre><code>@Column(nullable = false, columnDefinition = "VARCHAR(255)")
@Convert(converter = UriConverter.class)
private URI consulUri;
</code></pre>

As far as Hibernate is involved, it seems it has a bunch of <a href="https://docs.jboss.org/hibernate/orm/3.6/reference/en-US/html/types.html#types-value-basic" rel="nofollow noreferrer">provided type mappers</a>, including for <code>java.net.URL</code>, but not for <code>java.net.URI</code> (which is what we needed here).

blocks|key|3101162|text|我几乎尝试了这里提到的每一个步骤。都不起作用。下载mariadb。啊，真灵。我知道这不是一个解决方案，但这可能会帮助某人快速发现问题或给出临时解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3101163|Server+version:+10.2.10-MariaDB+-+MariaDB+Server
Protocol+version:+10
Server+charset:+UTF-8+Unicode+(utf8)|code-block|syntax|javascript|3101164|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

I tried almost every steps mentioned here. None worked. Downloaded mariadb. It worked. I know this is not a solution yet this might help somebody to identify the problem quickly or give a temporary solution.

<pre><code>Server version: 10.2.10-MariaDB - MariaDB Server
Protocol version: 10
Server charset: UTF-8 Unicode (utf8)
</code></pre>

blocks|key|335667|text|在我的例子中，这个问题是通过将Mysql列编码更改为'binary‘(数据类型将自动更改为VARBINARY)来解决的。也许我不能过滤或搜索该列，但我不需要这样做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|335668|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In my case that problem was solved by changing Mysql column encoding to 'binary' (data type will be changed automatically to VARBINARY). Probably I will not be able to filter or search with that column, but I'm no need for that.

blocks|key|339136|text|在我的例子Incorrect+string+value:+'\xCC\x88'...中，问题是o-umlaut处于分解状态。This+question-and-answer帮助我理解了o¨和ö之间的区别。在PHP中，我的解决方案是使用PHP's+Normalizer+library。例如，Normalizer::normalize('o¨',+Normalizer::FORM_C)。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|339137|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/38303793/how-to-identify-encoding-from-hex-values|1|https://www.php.net/manual/en/class.normalizer.php^0|5|11|2K|2|2N|1|41|1B|1Q|O|0|39|O|1|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]|$9|11|A|12|1|13]]|E|$]]|$1|F|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]|N|$5|I|J|K|E|$L|O]]]]

In my case, <code>Incorrect string value: '\xCC\x88'...</code>, the problem was that an o-umlaut was in its decomposed state. <a href="https://stackoverflow.com/questions/38303793/how-to-identify-encoding-from-hex-values">This question-and-answer</a> helped me understand the difference between <code>o¨</code> and <code>ö</code>. In PHP, the fix for me was to use <a href="https://www.php.net/manual/en/class.normalizer.php" rel="nofollow noreferrer">PHP's Normalizer library</a>. E.g., <code>Normalizer::normalize('o¨', Normalizer::FORM_C)</code>.

blocks|key|3101207|text|如果您碰巧在保存之前使用某个字符串函数处理该值，请确保该函数可以正确处理多字节字符。字符串函数不能做到这一点，例如，试图截断可能会在中间拆分单个多字节字符之一，这可能会导致此类字符串错误情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3101208|例如，在PHP中，您需要从substr切换到mb_substr。|offset|length|style|CODE|3101209|entityMap|0|LINK|mutability|MUTABLE|url|https://www.php.net/manual/en/function.mb-substr.php^0|0|D|6|M|9|M|9|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@$D|R|E|S|F|G]|$D|T|E|U|F|G]]|9|@$D|V|E|W|1|X]]|A|$]]|$1|H|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]]]

If you happen to process the value with some string function before saving, make sure the function can properly handle multibyte characters. String functions that cannot do that and are, say, attempting to truncate might split one of the single multibyte characters in the middle, and that can cause such string error situations.

In PHP for instance, you would need to switch from <code>substr</code> to <a href="https://www.php.net/manual/en/function.mb-substr.php" rel="nofollow noreferrer"><code>mb_substr</code></a>.

After noticing an application tended to discard random emails due to incorrect string value errors, I went though and switched many text columns to use the <code>utf8</code> column charset and the default column collate (<code>utf8_general_ci</code>) so that it would accept them. This fixed most of the errors, and made the application stop getting sql errors when it hit non-latin emails, too.

Despite this, some of the emails are still causing the program to hit incorrect string value errrors: <code>(Incorrect string value: '\xE4\xC5\xCC\xC9\xD3\xD8...' for column 'contents' at row 1)</code>

The contents column is a <code>MEDIUMTEXT</code> datatybe which uses the <code>utf8</code> column charset and the <code>utf8_general_ci</code> column collate. There are no flags that I can toggle in this column.

Keeping in mind that I don't want to touch or even look at the application source code unless absolutely necessary:

<ul>
<li>What is causing that error? (yes, I know the emails are full of random garbage, but I thought utf8 would be pretty permissive)</li>
<li>How can I fix it?</li>
<li>What are the likely effects of such a fix?</li>
</ul>

One thing I considered was switching to a utf8 varchar([some large number]) with the binary flag turned on, but I'm rather unfamiliar with MySQL, and have no idea if such a fix makes sense.

How to fix "Incorrect string value" errors?

单元测试

集成测试

SQL数据库

数据库

服务器

MariaDB

Windows

Python

Ubuntu

MySQL

在注意到应用程序由于不正确的字符串值错误而倾向于丢弃随机电子邮件后，我尝试并切换了许多文本列，以使用utf8列字符集和默认列排序(utf8_general_ci)，以便它可以接受它们。这修复了大多数错误，并使应用程序在遇到非拉丁语电子邮件时停止获取sql错误。尽管如此，一些电子邮件仍然导致程序命中不正确的字符串值错误：...

问如何修复“字符串值不正确”的错误？
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复“字符串值不正确”的错误？EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何修复“字符串值不正确”的错误？
EN