5 ms·
I tend to find people who argue with me against MySQL bring up things that haven't been true in a long time such as Unicode or NULL handling. I'd probably choo
by gav 6y ago
I tend to find people who argue with me against MySQL bring up things that haven't been true in a long time such as Unicode or NULL handling.
I'd probably choose Postgres over MySQL for a new project just to have the improved JSON support, but there's upsides to MySQL too:
- Per-thread vs per-process connection handling
- Ease of getting replication running
- Ability to use alternate engines such as MyRocks
- johannes1234321 6y agoMySQL also has great JSON features (json data type, virtual indexes onnit, multi-value (array) indexes, json_table, ....)
- ascom 6y agoMyRocks is a little bit janky in my experience - it doesn't support some transaction isolation levels, fails to handle some workloads that rely on locking (such as a job queue), has failed to upgrade MariaDB minor versions [0], has very sparse documentation, and overall has given me some amount of unexpected behavior. Though I'm willing to put up with it due to its incredible compression capabilities... [0]: https://jira.mariadb.org/browse/MDEV-22609 https://jira.mariadb.org/browse/MDEV-22609
- OOPMan 6y agoMySQL has definitely improved a lot since 5.0 but it still had a few warts.
- stickfigure 6y agoDoes MySQL have transactional DDL yet? Because if not, it is not a contender as a primary datastore.
- deleted 6y ago[deleted]
- hinkley 6y agoDoes that mean they fixed “utf-8” or that everyone is just supposed to know that it’s fucking bullshit and always has been? You can’t cut corners like that without inviting questionS about the character of the primary committers. The pecking order in software is about trust. People don’t let that stuff go easily, which is why you still see people harping on MongoDB. Once someone is labeled a liar And a cheat, everything they say that doesn’t add up is “guilty until proven innocent.” The utf-8 situation is on top of a bed of half truths. Things like publishing benchmarks with backends that don’t support isolation. A cornerstone of a good DB is handling concurrent access efficiently and correctly. Drawing attention to other benchmarks is a lie by omission. Better than just being incorrect for a decade, certainly, but still sketchy.