4 ms·
I know I made the decision in 2012 or so. The startup I was working at used Postgres for the server, and I didn't know anything about databases, so, okay, fine,
by prewett 3y ago
I know I made the decision in 2012 or so. The startup I was working at used Postgres for the server, and I didn't know anything about databases, so, okay, fine, whatever. Then they started an analytics team, which went with MySQL ... and ended up discovering that MySQL only handled up to 3-byte characters of UTF-8, which was a problem since the users of our game Chinese characters and lots of creative abuses of Unicode characters. My takeaway was that UTF-8 has always been at least 4 bytes (and I think it might have required 6 back then, which has since been walked back), and that any database which could not implement the spec of something fundamental like UTF-8 correctly was completely out of the realm of consideration.
- sgarland 3y agoMySQL had utf8mb4 support in 2010, but to be fair it wasn’t the default, and also depending on the row format indexing cols using it wasn’t possible. Like everything with MySQL, there were and are endless gotchas. Once you learn most of them it’s incredibly performant (and ProxySQL in front of it is amazing, and has way more capabilities than just connection pooling), but it’s definitely full of footguns.