https://tanguy.ortolo.eu/blog/article62/mysql-encoding en a blog about Debian and self-hosting Wed, 18 Jul 2012 12:58:00 +0000 PluXml https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342616315-1 https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342616315-1 @mirabilos : No problem, just expect that I make fun of your comments from time to time then. :-) (and do not hesitate to correct me when I say anything wrong, of course) Wed, 18 Jul 2012 12:58:00 +0000 Tanguy https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342614064-1 https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342614064-1 @Tanguy: funnily, you tend to choose topics I can’t help but “troll” on (although this is not strictly trolling; my utterances usually have some amount of truth behind them). Sorry about that. I really respect that you write a lot about technical stuff, but most of the time I find something (usually minor, which is why I rarely comment on them) wrong with the posts, technically, that bugs me. I have made the experience that half-knowledge can hurt worse than being unknowledgeable. Really, sorry. Nothing personal, and even nothing against your posts. This says more about me than about you. Wed, 18 Jul 2012 12:21:00 +0000 mirabilos https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342526047-1 https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342526047-1 @Nicolas : I was still thinking MySQL did not support the astral planes above the BMP at all, thanks you for the information. @mirabilos : You would not have anything constructive to say at all, would you? Tue, 17 Jul 2012 11:54:00 +0000 Tanguy https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342524973-1 https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342524973-1 LOL @ article ROTFLMAO @ comment from Nicolas Anyway, please do not write “dealing with MySQL databases”, it’s not a database. Tue, 17 Jul 2012 11:36:00 +0000 mirabilos https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342513651-1 https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342513651-1 « As you can see, it is quite modern in its default choice: if you do not specify which encoding you want to encode your database content into, it uses UTF-8. This way, it can save any database content, whatever characters it may contain. » afaik, there's a BIG trap here. According to the mysql documentation the "mysql utf8" is a only a 3bytes subset of the 4bytes "ietf utf8" set : it can only encode BMP values (thoses encodable on 3 bytes), if you want to save valid unicode values from SMP (thoses who need 4 bytes ; like "Mathematical Alphanumeric Symbols" set or the newly added "Emoticons" set) you should use the "mysql utf8mb4". * https://dev.mysql.com/doc/refman/5.6/en/charset-unicode-utf8mb4.html * https://tools.ietf.org/html/rfc3629#section-3 * https://en.wikipedia.org/wiki/Plane_(Unicode) Talk about obvious discrepancy :p Tue, 17 Jul 2012 08:27:00 +0000 Nicolas https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342502453-1 https://tanguy.ortolo.eu/blog/article62/mysql-encoding/#c1342502453-1 Unless of course you are seriously dealing with mysql, then you just take binary backups and not have this problem. Tue, 17 Jul 2012 05:20:00 +0000 Marcus