I reject the idea that MySQL's shitty unicode behavior is because it predates UTF8. Postgres is only one year younger.
-
>Reading UTF-8 white paper "Hmm. It calls for up to 4 bytes. But 3 bytes should be good enough for anyone" >Later, emoji "Well shit"
-
-
Their "utf8" (without _mb4) being a broken subset of UTF-8 seems a bigger deal than "Z" coming first alphabetically before "a". >_<
-
See also: https://twitter.com/sgrif/status/828686359099498496 … Connection level encoding has to match every field operated on with a bind param
- 5 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.