If you want to use utf8mb4, and character_set_server is not set to utf8mb4 in the my.cnf or my.ini file on your MySQL Server and you can't change this (for example utf8 is required for a database used by another application) you will need to add the connectionCollation=utf8mb4_bin parameter to your connection URL in order to use utf8mb4. Server character set considerations for Confluence When "DATA_TYPE" is replaced with "COLUMN_TYPE", the generated SQL is also valid for enum columns. The "DATA_TYPE" query currently fails for enum columns. MODIFY `FIELD` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin. The syntax is as follows: SELECT CONCAT ('anyStringValue:',IFNULL (yourColumnName, 'anyStringValue’)) AS anyVariableName FROM yourTableName To understand the above syntax, let us create a table. MODIFY `FIELDTYPE` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin, You can use CONCAT () method to concatenate values while IFNULL () method is used to handle NULL values. For example,ĪLTER TABLE `changeitem` MODIFY `FIELDTYPE` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin ĪLTER TABLE `changeitem` MODIFY `FIELD` varchar(255) CHARACTER SET utf8mb4 COLLATE utf8mb4_bin Query execution time can be reduced by combining multiple ALTER statements for the same TABLE (but different columns) into a singular statement, which avoids MySQL having to process the whole table multiple times. For performance reasons you may wish to optimize the resultant queries by hand before execution on the database, particularly if the tables being modified have hundreds of thousands to millions of rows. Upon executing the above queries, a list of individual ALTER statements is generated for each table and column. Not all versions of Jira and Confluence support utf8mb4 (which provides support for 4-byte characters). You must ensure your database has the correct collation for the application it will be used with.Ĭollation in MySQL can be complicated because you can have a separate collation set at:Īdditionally, the information inside a column may be encoded incorrectly as well - causing the data in that column to be displayed incorrectly. In newer versions of Atlassian applications, collation changes may become more strict - i.e, an application requires a certain collation. The collation determines how results are sorted and ordered. After the solution is implemented, please test the application thoroughly to ensure everything works correctly and as expected. If the recommended method for some reason is not suitable for your scenario, please follow this article to manually fix the collation at the database server side. Follow our Switching Databases using an XML backup to migrate from the old database (with the incorrect collation) to the new one, with the correct collation.Create a new database with the required collation as per the appropriate documentation (for example Connecting JIRA to a Database).Our recommended method for migrating databases is as follows Direct database manipulation is not covered by our Atlassian Support Offerings and should be up to your DBAs discretion.
0 kommentar(er)
