3 ms·
Early MySQL versions made egregious design choices like quietly ignoring missing foreign keys and enum typos, truncating long strings, and randomly choosing row
by erik_seaberg 2y ago
Early MySQL versions made egregious design choices like quietly ignoring missing foreign keys and enum typos, truncating long strings, and randomly choosing rows from groups.
https://web.archive.org/web/20230922210124/https://grimoire.ca/mysql/choose-something-else/#data-processing https://web.archive.org/web/20230922210124/https://grimoire....
- sgarland 2y agoYeah, it was bad. What kills me is SQLite has its own absurd set of gotchas [0] yet is seen as amazing and wonderful by devs. PKs can have NULLs? Sure! Strings can have \0 in the middle of them? Why not? FKs aren’t enforced by default? Yeah, who needs referential integrity, anyway? My only conclusion is that the majority of devs don’t actually read documentation, and rely purely on the last blog post they read to influence their infrastructure decisions. [0]: https://www.sqlite.org/quirks.html https://www.sqlite.org/quirks.html
- hu3 2y agoUnderstanding and memorizing shortcomings and quirks takes time and effort. Most devs just go with whatever the influencer du jour says is good. "Nobody ever got fired for choosing insert_currently_hyped_tech_here"