3 msΒ·
πΏπππ πππππ ππππ ππππππππ ππππ πππ π΄ ππππ ππ. πΉππ π΄ πππ πππ πππ πππππ ππ πππππ ππππππππππ οΏ½
by netheril96 12y ago
πΏπππ πππππ ππππ ππππππππ ππππ πππ π΄ ππππ ππ. πΉππ π΄ πππ πππ πππ πππππ ππ πππππ ππππππππππ ππ πππππ πππππ ππππ πππππ'π πππππππ ππππππππππ.
- masklinn 12y agoExcept when the site in question is completely broken wrt astral codepoints. Which is unexpectedly common as MySQL's "utf8" can't handle codepoints outside the BMP and will just truncate text at the first astral codepoint[0]. You need MySQL 5.5.3 (because adding a whole new encoding in a minor version makes perfect sense) and "utf8mb4" (because why would a codec called "utf8" actually do UTF8?). And then the regex are probably broken because it's PHP and developers use neither UNICODE mode nor properties (PCRE's "\w" will not match all unicode letters, you need "\p{L}" for that, also note that e.g. "π" is a symbol not a letter, although "πΉ" is a letter) [0] https://mathiasbynens.be/notes/mysql-utf8mb4 https://mathiasbynens.be/notes/mysql-utf8mb4
- TazeTSchnitzel 12y agoMySQL is horrible for all the same reasons PHP is horrible, and this applies to Unicode too, except PHP is actually trying to fix its Unicode problems (UTF8 is the default now, moves towards adding a UString class), while MySQL isn't fixing them.
- egypturnash 12y agoLike π»ππππππ! https://twitter.com/egypturnash/status/535105548761309184 https://twitter.com/egypturnash/status/535105548761309184