Re:Unicode is, in 2012, still “cutting edge.”
by haberman on Tuesday July 10, 2012 @05:53PM
(#4226418)
A data-loss bug is far more serious than anything about sorting. MySQL has an encoding called "utf8" -- if you can't count on it to round-trip UTF-8 data without data loss, that is a serious problem IMO, documented or not.
[ Parent
| on HN ]
Re:Unicode is, in 2012, still “cutting edge.”
by koenigdavidmj on Tuesday July 10, 2012 @06:04PM
(#4226480)
The real problem is that MySQL accepts and silently drops this data that it cannot handle. It has a nasty tendency to silently drop data rather than error out.
Re:Unicode is, in 2012, still “cutting edge.”
by crazygringo on Tuesday July 10, 2012 @09:24PM
(#4227226)
Really? I've done a lot of data importing into MySQL, and it always gives me a warning that tells me the invalid Unicode code point. It doesn't generate an error, but it definitely generates a warning. You need to make sure whatever client/library you're using is passing that on to you, though.
Re:Unicode is, in 2012, still “cutting edge.”
by ubernostrum on Wednesday July 11, 2012 @01:46AM
(#4227928)
It doesn't generate an error, but it definitely generates a warning. You need to make sure whatever client/library you're using is passing that on to you, though.
That right there is the problem.
Other DBs, when you do something they can't handle, bail with a full-fledged error that stops what you're doing. MySQL doesn't do that for quite a few data-losing cases, and that's incredibly dangerous.