3 ms·

Maybe it's time for MySQL to make "utf8" actually mean UTF-8 then (https://medium.com/@adamhooper/in-mysql-never-use-utf8-use-utf8mb4-11761243e434 https://mediu

• treve 7y ago
  > Although utf8 is currently an alias for utf8mb3, at some point utf8 will become a reference to utf8mb4. To avoid ambiguity about the meaning of utf8, consider specifying utf8mb4 explicitly for character set references instead of utf8. https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8.html https://dev.mysql.com/doc/refman/8.0/en/charset-unicode-utf8... Can't fault a database vendor being conservative, but looks like this is planned. Maybe this will be a 9.0 thing.
• smacktoward 7y ago
  They probably couldn't even if they wanted to, by this point there will be too much software out there depending on "utf8" meaning "MySQL's weird proprietary hacked-up version of UTF-8". The only real solution is to hammer home the message that "utf8mb4" is what you put into MySQL if you want UTF-8.
  • cosarara 7y ago
    There are acual problems too, when switching from utf8mb3 to utf8mb4, because of maximum varchar length in indices: https://stackoverflow.com/questions/48500355/mysql-character-set-utf8mb4-varchar-length https://stackoverflow.com/questions/48500355/mysql-character...