4 ms·
Hey, author here -- it is a bit odd and also possibly immature to be so harsh on MySQL apropos of nothing. That said, I intended more to be pro-Postgres rather
by hardwaresofton 4y ago
Hey, author here -- it is a bit odd and also possibly immature to be so harsh on MySQL apropos of nothing. That said, I intended more to be pro-Postgres rather than anti-MySQL (it's a great piece of software, other DBs and Postgres learn from it all the time, zheap[0] exists to replicate what they've built, for example).
I also have to admit that I definitely want postgres every time I see MySQL. Maybe I need to read more on just how easy and amazing MySQL can be. Links welcome!
[0]: https://cybertec-postgresql.github.io/zheap/ https://cybertec-postgresql.github.io/zheap/
- rockwotj 4y agoWould love to hear some concrete reasons here. What about postgres makes you avoid MySQL?
- hardwaresofton 4y agoThere are a ton -- in general flexibility, wealth of enterprise-grade resources and support, community, speed of improvements and rock solid operation. For just one real concrete reason, postgres's extension ecosystem is second to none, AFAIK.
- ttfkam 4y agoFor me it's a sea of green when MySQL makes me see red. https://www.sql-workbench.eu/dbms_comparison.html https://www.sql-workbench.eu/dbms_comparison.html Top 3: transactional DDL, range types, event triggers
- hardwaresofton 4y agoChanging my answer to transactional DDL. I use Postgres so much I literally forgot that it isn't always there.
- lsaferite 4y agoTransactional DDL is the biggest one for me (comparing MySQL and Postgres).