4 ms·
Well...I love MySQL but there was a time when it was anything but rock solid. It was pretty painful until InnoDB replaced MyISAM in 2010 as the default storage
by hodgesrm 5y ago
Well...I love MySQL but there was a time when it was anything but rock solid. It was pretty painful until InnoDB replaced MyISAM in 2010 as the default storage engine. After that it became rare to lose data.
- dijit 5y agoExcept in cases where the constraints may be violated and it just inserts the next nearest thing. Or the times where the transaction isolation just abruptly ends and commits your transaction midway; leaving no chance of a rollback. Or when you alter a column to a new type and the cast doesn’t work in a few cases and just leaves corrupted garbage on every row. Or when the replication misses a few transactions and your replica now looks different to your primary. (These aren’t hypothetical, these are things I’ve seen)
- derekperkins 5y agoHave you seen any of those since 5.7?
- hodgesrm 5y agoDon't get me wrong, there are still occasional problems. Most of those I've encountered have been applications misusing MySQL. We can debate whose fault that is. But at least people stopped doing REPAIR TABLE after hard restarts of MySQL. It's been a long time since I last had to do that.