When you see outrage in response to matters like codes of conduct, think of an imaginary box. The extents of this box define the limits of socially acceptable expression. If any expression falls outside of the box, the response is outrage. Examples that fall outside of the box could be things like using a company email address for certain kinds of speech, or citing behaviors external to a community in making a conduct-related decision.
I talk to people from the UK pretty regularly, I watch a lot of BBC programming, I read a lot of books by authors from the UK, but sometimes they will suddenly use a word I've never heard in my life, and I'm beginning to think they are pranking us, and every other person from the UK is in on the joke, and just validates whatever the other person says!
A coop PvE game for two dads and three sons?
A shooter, preferably. Any recommendations, #mastodon guys? The youngest lad is 10, so as little violence as possible. Thanks 😉
I'm now almost through migrating PG to MySQL with Stored Procedures only. Ended up with 140 Stored Procedures. The insights I gained into the business domain are incredible.
Now there are some bigger challenges:
How to test an API that literally has hundreds of different endpoints + parameter combinations against the new version
How to transfer data of a 100GB+ sized PG to MySQL in a timely manner so that downtime is reduced to < 15 minutes.
Or even more challenging: how to transfer 60 PG tables to MySQL with a "slightly" optimised schema and a buggy pg_dump exporter, that wrongly decodes JSON values into unreadable data (bug filed 2015, maintainers not interested)? Or a buggy PG_MySQL Foreign Data Wrapper that fails with Boolean and JSON columns (bug filed in 2020, maintainers not interested)?
I've tried 10 different tools that advertise themself as a solution to this and not a single one was able to overcome these challenges (issues with JSON, Timestamp and Boolean columns). Any hints?
So if "interoperability" is a goal of the SQL standard, it clearly failed. If "interoperability" is a benchmark for open source databases, Postgres doesn't shine at all. All the features that make Postgres "so good" (like ARRAYs which are unknown to every other SQL database, BOOLs and Custom Types) are in fact locking your project in like forever.
However, I'm not the one who gives up easily. I'll likely end up with a hand-rolled migration tool and then sell it to make a fortune off it, for all those non-existing devs who want to migrate away from Postgres. :neofox_evil:
@louis Thank you for the response - there are a few surprising things in there!
(eg: Personally speaking, I've always found the PG docs to be superb, and I've always thought of PG as being in extremely close adherence to the SQL spec)
PG aside, any particular reason for MySQL over MariaDB? (Especially if performance is a consideration)
