Replying to Avatar Bourbonic Plague

I worked 36 hours this weekend to get MySQL out of my life. There was no external urgency driving me to do that, I just couldn’t stop thinking about it because I want to solve the problem so bad there was nothing else to do but work on it. I woke up chewing on the problem and I passed out each night at 11pm doing the same.

“That’s crazy, you should retire to full time shitposting, you would be much happier.”

Seems to be working great for all the rich bitcoiners who are trying that strategy.

I could golf 6 days a week like my dad did for a decade after he retired early. But I’ve played golf and I know that puzzle isn’t nearly as interesting as the puzzles I’m working on right now. He just up and quit golfing almost a decade ago like he was retiring a second time. I never asked him why because the real question I didn’t have the heart to ask was: why did it take you so long?

People spend all their time bitching about nobody taking responsibility for solving the hard problems around them and yet some of those same people spend all their time trying to come up with ways to avoid taking responsibility for solving any of those problems.

“That’s fiat, bro.” Ok bro, enjoy your queer life of leisure.
Avatar
TomFinnegan22 2y ago

As someone just getting started with MySQL, what should I know that you do?

Reply to this note

Please Login to reply.

Discussion

Avatar
Bourbonic Plague 2y ago

I chose MySQL 16 years ago when Postgres was still a bit too immature and was lacking the replication features that I needed at the time.

Now, Postgres is a much easier choice than MySQL.

Just one MySQL example: it reuses auto_increment values that were used but deleted when the server restarts. That is supposedly fixed in version 8.0, but it has been broken in all versions before that since 2003 including a version (5.7) that doesn’t reach end of life until this October.

If you have related child records that don’t get deleted when the parent record gets deleted and the foreign key is based on an auto_increment column, you can end up with child records pointed at new records that got assigned the old parent ID after the server restarts.