Hi,
We just encountered an error where a user entered an emoji into a form's text description, which then failed to save in the MySQL database. Apparently this is due to the collation that is set on the database (utf8_general_ci) does not support such characters.
(FYI, the character was & # 55357; & # 56842; - aka smiling face with smiling eyes: http://apps.timwhitlock.info/unicode/inspect/hex/1F60A)
What is the recommended way to handle such data?
Thanks,
Mike
Discussion posts and replies are publicly visible
In our case it was actually in the name field returned by the Google Places API. It was somewhat unexpected to say the least.
...and yes, the immediate fix was to strip out the "illegal" characters with the following expression:
joinarray( char( reject( fn!exact, code( ri!place.name ), 000000 ) ) )
Where 000000 is the unicode value of the offending character.