Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-32336

deb: 50-server.cnf:collation-server = utf8mb4_general_ci dated- replace with utf8mb4_uca1400_ai_ci

Details

    Description

      Wordpress moved to utf8mb4_unicode_ci / utf8mb4_unicode_520_ci where available and left the utf8mb4_general_ci behind. It seems odd that the default server-collation is utf8mb4_general_ci.

      Now that we have uc1400 we should use this in new installations.

      will need updating: https://mariadb.com/kb/en/differences-in-mariadb-in-debian-and-ubuntu/

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. MDEV-32975 Default charset doesn't work with PHP MySQLi extension

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed
          relates to

          Bug - A problem which impairs or prevents the functions of the product. MDEV-34304 Improve FK constraint error messages was: Foreign key constraint is incorrectly formed on 11.4.2. It works on 10.11.7

          • Major - Major loss of function.
          • Stalled

          Activity

            Ascending order - Click to sort in descending order
            serg Sergei Golubchik added a comment -

            bar, comments?

            serg Sergei Golubchik added a comment - bar , comments?
            bar Alexander Barkov added a comment - - edited

            I suggest if change the default my.cnf, then as follows:

            character-set-server=utf8mb4
            		 
            character-set-collations=utf8mb4=uca1400_ai_ci

            This:

            • will automatically change collation-server to uca1400_ai_ci
            • will on the SQL level, e.g. in CREATE scripts, automatically resolve: 

              CHARACTER SET utf8mb4

              to

              CHARACTER SET utf8mb4 COLLATE uca1400_ai_ci

            If we don't set character-set-collations=utf8mb4=uca1400_ai_ci, then in all contexts where we have CHARACTER SET without COLLATE, it will still be resolved to utf8mb4_general_ci, which is not desirable.

            bar Alexander Barkov added a comment - - edited I suggest if change the default my.cnf, then as follows: character-set-server=utf8mb4 character-set-collations=utf8mb4=uca1400_ai_ci This: will automatically change collation-server to uca1400_ai_ci will on the SQL level, e.g. in CREATE scripts, automatically resolve: CHARACTER SET utf8mb4 to CHARACTER SET utf8mb4 COLLATE uca1400_ai_ci If we don't set character-set-collations=utf8mb4=uca1400_ai_ci , then in all contexts where we have CHARACTER SET without COLLATE , it will still be resolved to utf8mb4_general_ci, which is not desirable.

            People

              danblack Daniel Black
              danblack Daniel Black
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.