I’ve been running into several problems with restoring MySQL backups. Namely, the backups come from an environment other than the one I’m working in and I’m forced to remove superuser commands contained in the backups.
The problem is when trying to remove those commands I’m constantly getting UTF-8 encoding errors because there are loads of invalid character sequences.
Why would MySQL encode a backup as UTF-8 if the data isn’t actually UTF-8? This feels like bad design to me.
Yet as a developer I’m expected to deal with crazy stuff like ASCII, weird encoding standards for email, Punycode, etc. but MySQL developers couldn’t figure out how to encode characters properly while dumping the database?
I’d love to be a superior asshole because I use ⭐Microsoft SQL⭐ hair flip but they charge you for convenience and call it the industry standard which I find kind of abhorrent
sorry to trauma dump
Oh don’t get me started on SQL Server either. That’s the most maintenance-heavy, hands on approach I’ve ever seen. “Do one thing and do it well” doesn’t apply, you’ve got to manage every dumb knob that shouldn’t matter to you as an end-user.