-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
4
-
Summary
Bitbucket Server currently only supports the utf8 character set on MySQL and MariaDB databases, which only allows Unicode characters in the range U+000000 to U+00FFFF to be represented. Certain characters outside this range (such as emojis like 🙌 - column Symbola) fail with database errors in various contexts, such as being added to Pull Request comments.
Database migration from a non-MySQL database containing Unicode characters above U+00FFFF into MySQL also fails with errors.
The utfmb4 character set available in some versions of MySQL can represent Unicode characters above U+00FFFF, but this character set is not currently supported by Bitbucket Server.
Workarounds
1. Remove the affected value by query to the instances current database. Since the error is show the affected character which is \xF0\x9F\x99\x8C in migration fail, web searched the \xF0\x9F\x99\x8C and paste the image in the SQL query which appears as {{ 🙌}}.
Stop the instance and perform the following query.
SELECT id FROM sta_comment WHERE comment_text LIKE ' 🙌';
DELETE FROM sta_comment WHERE id = <id_value>;
Restart the instance and migrate to the new database.
2. Migrate to another database type (e.g., PostgreSQL) instead of MySQL.
- is related to
-
JRACLOUD-36135 Add support for 4 byte characters in MySQL connection
- Closed
-
JRASERVER-36135 Add support for 4 byte characters in MySQL connection
- Closed
- relates to
-
BSERV-18945 Update the Supported Platforms pages to indicate MySQL on utf8mb4 is not supported
- Closed