MySQL and utf8mb4 (4-byte unicode support)

[JustAMacUser]

[fox]

in all honesty i'm not sure if this is worth the trouble for some worthless emojis and stuff. if people really want those that much they can use a proper database server i.e. postgres.

i however don't see it as something any sizable percentage of tt-rss userbase would care about in any shape or form. i.e. i don't remember anyone here complaining about missing extended utf characters in posts.

also, not only this is an extensive schema overhaul for arguably little gain there's also additional mysql version requirements - i think it's 5.5.something needed for utf8mb4 with maybe additional requirements on client libraries. there's a huge potential here for breakage / tears.

i understand that this change will remove a hack and make things neater in a way and i appreciate the effort you went through but in the end i really don't think its worth it.

[JustAMacUser]

Not a problem. The transition is certainly not without its challenges. At the very least this thread can serve to provide more info to others about why things are the way they are.

[fox]

yep more input would be appreciated

speak up emoji lovers

[DeviousNull]

[fox]

i think that's what we're doing anyway on most article fields (see rssfuncs.php:782).

as far as i could see the pile of poo emoticon gets properly replaced to the utf ? thing, so i'm not sure why additional preg_replaces are needed.

DeviousNull, which tt-rss version are you running?

[DeviousNull]

Well, now this is embarrassing. My git repo didn't have origin pointed at your repository, and so I wasn't getting updates. When I fixed that and updated, the problem went away.

Sorry about that.