Trying to post emoji on these boards results in the string getting cut off before the emoji character. This is an issue with database encoding.


AB2.5 sets DB encoding to latin1, which isn't right considering we're storing UTF8.


But even when setting the encoding to UTF8, the aforementioned bug still happens. Because UTF8 support in MySQL is a pile of hacks and doesn't support characters with more than 3 bytes.


When setting encoding to utf8mb4, emoji characters are handled fine. Maybe seems like a lot of work for something minor (letting people post emoji crap), but on the other hand, there's the possibility that someone writes a big post with emoji crap at the beginning, and there it goes.


'a lot of work' because changing encoding on an existing database isn't magic. You'd need to change it on every varchar/text field because MySQL is dumb like that. And also modify the board to specify the right encoding when connecting to MySQL.

____________________
Kuribo64 - melonDS

want some revolution in your coffee?

I just converted K64's database to utf8mb4, everything went allright so far. Could hand you the .sql file I used as a base.


Thing is, K64's database was already UTF8 before that, so it went smoothly. Going from latin1 to UTF8 is more involved, you need some trickery to keep MySQL from trying to convert the already-UTF8 data into UTF8. A solution may be creating a new empty database with proper UTF8 fields, exporting the old one and reimporting. I've been dealing with that shit before too, but I don't remember the details.

____________________
Kuribo64 - melonDS

want some revolution in your coffee?