@newt fat fingered the buttons again ![]()
@nexus_plasma @m0urs nix da, alman hat die klappe zu halten:
> Liebe Leserinnen und Leser,
wir bitten um Verständnis, dass es im Unterschied zu vielen anderen Artikeln auf unserem Portal unter diesem Artikel keine Kommentarfunktion gibt. Bei einzelnen Themen behält sich die Redaktion vor, die Kommentarmöglichkeiten einzuschränken.
Die Redaktion
![]()
@Nazareno maybe as a counter to the western collectivist shit-show, but it really is replacing one evil with another.
@Nazareno the alternative being? :)
@cjd I believe in canada that's considered practicing medicine w/o a license
@m0urs der zug ist halt leider abgefahren. 76% haben mindestens zwei dosen bekommen. 62% nen booster oben drauf.
und wenns überall so läuft wie in meinem umfeld grade zu beobachten, gehts grade erst los mit den problemen.
Taibredo dances for you.
If this flame is beautiful, ⭐ or boost this post to improve its chances for future breedings.
#generativeArt
Meet Ovarakuki, child of Nor and Pashaea.
They are the product of 21 generations of breeding.
They are famously gregarious.
If this flame is beautiful, ⭐ or boost this post to improve its chances for future breedings.
#artBot
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.
state licensed lolbert and hypernatalist with a breeding kink. never watched rick & morty and i'm proud of it.
don't only rely on my words, read what happy customers wrote about me: "10/10 would buy again", "top seller, great value", "wildly incorrect", "teil des problems", "without imagination", "Repeated provocation using copy/paste.", "if you take a dump in my mentions, I just might notice the smell", "log out and never login again", "Du redest wirr.", "My brother in Christ, this is such a ridiculously dumb statement that I will no longer entertain this silly conversation.", "Auf Derailing-Diskussionen habe ich keine Lust. Finger über dem Blocken-Knopf.", "Wie gesagt, du kannst der Diskussion inhaltlich nicht folgen."
➡️ NO PRESSURE ⬅️ 💄NO DIAMOND💍
one day at a time.