Re:Unicode is, in 2012, still “cutting edge.”
by masklinn on Wednesday July 11, 2012 @02:28AM
(#4228041)
> Honestly it's probably better they don't change the behavior of an existing MySQL character set.
Or they could just have implemented it correctly to start with, considering unicode "support" was introduced in mysql 4.1.
In 2005.
> Who knows what software out there depends on it breaking on 4-byte characters, or whatnot.
Then again, mysql routinely drops and corrupts data anyway, I'm sure its "users" could have dealt with it corrupting data slightly less than before.
Creating a new character set `utf8mb4` was the right thing to do, as annoying as it is. Just clearly label the `utf8` collation as 'deprecated' in the docs or something.