Ran into an issue after upgrading from MariaDB 10.1 to MariaDB 10.3, using the latest HyperDB (1.7). On a site with database tables using the
utf8mb4charset but the wp-config constant set to
utf8, a Twitter oembed with an emoji repeatedly caused an “Incorrect string value” database error and it could not cache to the
postmetatable. Toggling the
utf8mb4resolved the issue.
Without HyperDB, with
utf8, WordPress will allow or disallow emojis based on the table charset. This would be my expectation of HyperDB behavior. I have only encountered it in this configuration (MariaDB 10.3, WordPress 4.9.16, HyperDB 1.7) so I don’t know how prevalent it is across database versions.
- The topic ‘DB errors with utf8 charset / utf8mb4 tables with MariaDB 10.3’ is closed to new replies.