MySQL’s utf32 and utf8mb4 (as well as standard UTF-8) can directly store any character specified by Unicode; the former is fixed size at 4 bytes per character whereas the latter is between 1 and 4 bytes per character. utf8mb3 and the original utf8 can only store the first 65,536 codepoints, which will cover CJVK (Chinese, … 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
If you’re using utf8mb4, and you have unique indexes on varchar columns that are greater than 191 characters in length, you’ll need to turn on innodb_large_prefix to allow for larger columns in indexes, because utf8mb4 requires more storage space than utf8 or latin1. Add the following to your my.cnf file. [mysqld] innodb_file_format=barracuda innodb_file_per_table=1 innodb_large_prefix=1 init_connect=”SET … 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
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
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
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
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