Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. See Handling MySQL 4-byte character support problems for some steps that can be taken to work around this

  2. Migrate to a database that is known to fully support 4-byte characters out-of-the-box, like PostgreSQL

  3. As of MySQL 5.7, it may be possible to use the utf8mb4 charset with JIRA 7.3.  We cannot personally vouch for this and so caution is advised: https://confluence.atlassian.com/jirakb/jira-does-not-work-with-emoji-4-byte-characters-429919955.html

  4. Convert the column being complained about to UTF-8. For example, updating the AUDITEVENTS table EXCEPTION column to UTF-8 in the JIRA database would be done with:
    ALTER TABLE `jira`.`AO_78C957_AUDITEVENTS` MODIFY COLUMN `EXCEPTION` TEXT CHARACTER SET utf8 COLLATE utf8_general_ci DEFAULT NULL;

  5. Some customers have found upgrading to using ‘mysql-connector-java_8.0.23’ database drivers and using the ‘utf8mb4’ character set and ‘utf8mb4_bin’ collation as described in the Atlassian database connection instructions can mitigate this issue:
    * https://confluence.atlassian.com/adminjiraserver0813/connecting-jira-applications-to-mysql-5-7-1027137456.html
    * https://confluence.atlassian.com/adminjiraserver0813/connecting-jira-applications-to-mysql-8-0-1027137457.html

...