Your version does not support that character set, I believe it was 5.5.3 that introduced it. You should upgrade your mysql to the version you used to export this file. The error is then quite clear: you set a certain character set in your code, but your mysql version does not support it, and therefore … Read more
If you need MySQL to support 4-byte UTF-8 characters (which is normally considered part of UTF-8), you need to use the character set utf8mb4, not utf8. utf8mb4 was first supported in MySQL 5.5.3.
MySQL’s utf8 charset is not actually UTF-8, it’s a subset of UTF-8 only supporting the basic plane (characters up to U+FFFF). Most emoji use code points higher than U+FFFF. MySQL’s utf8mb4 is actual UTF-8 which can encode all those code points. Outside of MySQL there’s no such thing as “utf8mb4”, there’s just UTF-8. So: Does … Read more
It’s the character at the end of the tweet that’s causing the problem. It looks like an ’emoji’ character aka japanese smiley face but it’s not displaying for me in either Chrome or Safari. There are known issues storing 4byte utf characters in some versions of MySQL. Apparently you must use utf8mb4 to represent 4 … Read more
Collation and character set are two different things. Character set is just an ‘unordered’ list of characters and their representation. utf8mb4 is a character set and covers a lots of characters. Collation defines the order of characters (determines the end result of order by for example) and defines other rules (such as which characters or … Read more
Most iOS emojis use code points above the Basic Multilingual Plane of the Unicode table. For example, 😄 (SMILING FACE WITH OPEN MOUTH AND SMILING EYES) is at U+1F604. Now, see http://dev.mysql.com/doc/refman/5.5/en/charset-unicode.html. MySQL before version 5.5 only supports UTF-8 for the BMP, which includes characters between U+0000 and U+FFFF (i.e. only a subset of actual … Read more
character_set_client, _connection, and _results must all be utf8mb4 for that shortcake to be eatable. Something, somewhere, is setting a subset of those individually. Rummage through my.cnf and phpmyadmin’s settings — something is not setting all three. If SET NAMES utf8mb4 is executed, all three set correctly. The sun shone because it is only 3-bytes – … Read more
4 byte Unicode characters aren’t yet widely used, so not every application out there fully supports them. MySQL 5.5 works fine with 4 byte characters when properly configured – check if your other components can work with them as well. Here’s a few other things to check out: Make sure all your tables’ default character … Read more
UTF-8 is a variable-length encoding. In the case of UTF-8, this means that storing one code point requires one to four bytes. However, MySQL’s encoding called “utf8” (alias of “utf8mb3”) only stores a maximum of three bytes per code point. So the character set “utf8″/”utf8mb3” cannot store all Unicode code points: it only supports the … Read more
MySQL’s utf8 permits only the Unicode characters that can be represented with 3 bytes in UTF-8. Here you have a character that needs 4 bytes: \xF0\x90\x8D\x83 (U+10343 GOTHIC LETTER SAUIL). If you have MySQL 5.5 or later you can change the column encoding from utf8 to utf8mb4. This encoding allows storage of characters that occupy … Read more