> and most of us got burned by MySQL on that one at some point before we got here Using 3 bytes per codepoint for UTF8 was the one that got me to switch (boy w

> and most of us got burned by MySQL on that one at some point before we got here Using 3 bytes per codepoint for UTF8 was the one that got me to switch (boy wasn't that fun to discover). Yes it was fixed a while ago now, but it wasn't fixed when I needed it and so I switched to PostgreSQL and never looked back.