don’t know the artist, just like the comic. check ‘slow query log’, you heathens.
You must log in or # to comment.
This gives me flashbacks to when I took over a small call center as there DBA.
Part of their data was in access, part of it was in notepad, and the rest was in a shoddy looking sql database.
It took me two years to get everything into a data warehouse.
But some of those queries. Oof
was joke, ‘kfc has quesadillas?’
👀
People like to shit on MySQL, I get it, but this is just stupid. No relational database on this planet could handle such an unoptimized situation in adequate time.
If you ignore the “no indexes” part (can’t request that in normal SQL anyway) then PostgreSQL absolutely can handle queries like that.
With indexes, so can MySQL or MariaDB. That’s why I said “unoptimized”. Postgres is certainly superior when it comes to more complex or analytical queries, but that’s because MySQL/MariaDB simply weren’t MADE for these kind of situations. And even postgres will struggle with an unoptimized, data-intensive workload. I’ve seen those in the wild.
It’s like shipping a formula 1 car into the desert and wondering why you’re last in the desert rally.
