Yes, I had this case too, I think it's the default charset of the database that breaks this. To remedy, I added this in my .cnf file

init_connect = 'SET collation_connection = utf8mb4_unicode_ci'
init_connect = 'SET NAMES utf8mb4'
character-set-server = utf8mb4
collation-server = utf8mb4_unicode_ci
skip-character-set-client-handshake