Interesting to note is that MySQL was first released in 1995. Which means that only for one year of its existence were there less than 65536 characters.
Re:Unicode is, in 2012, still “cutting edge.”
by klodolph on Tuesday July 10, 2012 @09:59PM
(#4227348)
Yes, but at the time, UTF-8 could encode up to 31 bits per character using six-byte sequences. It has since been restricted to four-byte sequences at the longest.
> seems to have done so less than a year ago
More than 2 years ago. March 2010.
Re:Unicode is, in 2012, still “cutting edge.”
by excuse-me on Tuesday July 10, 2012 @04:59PM
(#4226169)
But when did people really start using more than the 16bit unicode chars?
> But when did people really start using more than the 16bit unicode chars?
1996.
China even made it a legal requirement for computer systems in 2000, through mandating GB 18030.
There's the Private Use Area if nothing else. There is NO excuse to not support anything other than the BMP. Adding support is trivial unless you have been using UTF-16 in the erroneous belief that it's two bytes long always (in which case you've really been using UCS-2).
Unicode 2.0 introduced multiple planes, i.e. more than 65536 characters. That was in 1996. If that was the case, then MySQL has had more than one-and-a-half decades to introduce multiple planes and seems to have done so less than a year ago. I disagree with being 'redefined out from under them', when it was defined a year after MySQL started, at a time when it probably didn't even have Unicode support yet anyway.