Re:Why infrastructure engineers prefer MySQL
by benjamir on Tuesday January 18, 2022 @03:01AM
(#29976368)
This is close to ridiculous.
I have to manage both types of DBMS.
Postgres never failed, the concepts are harder to grasp and it thus isn't easy to overcome every hurdle immediately.
MySQL on the otherhand failed in so many ways that I stopped counting.
What hit us the most:
* Exports that weren't importable, broken (fields larger in export than allowed?!?) -- or read: a database in a state that wasn't able to go into a backup == garbage
* Imports silently ignoring constraints (yeah, once you know all the restrictions, that's manageable, but what a horrible DBMS!)
* ...
We only keep using it for legacy projects were migrating away isn't worth it.
I have to manage both types of DBMS.
Postgres never failed, the concepts are harder to grasp and it thus isn't easy to overcome every hurdle immediately.
MySQL on the otherhand failed in so many ways that I stopped counting. What hit us the most: * Exports that weren't importable, broken (fields larger in export than allowed?!?) -- or read: a database in a state that wasn't able to go into a backup == garbage
* Imports silently ignoring constraints (yeah, once you know all the restrictions, that's manageable, but what a horrible DBMS!)
* ...
We only keep using it for legacy projects were migrating away isn't worth it.