Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by astrange on Wednesday January 12, 2022 @09:02PM
(#29915895)
MySQL doesn't have to know that a db is UTF8 for you to store UTF8 in it. You're not necessarily using its collation functions or anything.
My understanding is replication and setting up MySQL is still easier than Postgres; it definitely was 10 years ago, that's why it's part of LAMP. The data loss issues were fixed forever ago when it switched to InnoDB.
Google AdWords and Facebook both use(d) MySQL a lot and I assume they knew about Oracle and Postgres at the time they were built…
Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by rrdharan on Wednesday January 12, 2022 @09:54PM
(#29916258)
> Google AdWords and Facebook both use(d) MySQL a lot and I assume they knew about Oracle and Postgres at the time they were built…
Why would you assume that? Both of the companies were tiny and full of children when these decisions were made. And Oracle was expensive and a non-starter for explosive horizontal scale.
Re:In MySQL, use “utf8mb4” instead of “utf8” (2016)
by astrange on Sunday January 16, 2022 @10:29PM
(#29963035)
Well, because I remember 2005 and the Postgres people were just as into posting about how superior it was as they are now.
(Where they had a point because MySQL hadn't switched to InnoDB yet.)
Right up until one of your users tries to use an emoji, apparently.