[MDEV-32336] deb: 50-server.cnf:collation-server = utf8mb4_general_ci dated- replace with utf8mb4_uca1400_ai_ci Created: 2023-10-01  Updated: 2024-01-30  Resolved: 2023-10-19

Status: Closed
Project: MariaDB Server
Component/s: Platform Debian
Fix Version/s: 11.3.1

Type: Task Priority: Major
Reporter: Daniel Black Assignee: Daniel Black
Resolution: Fixed Votes: 0
Labels: None

Issue Links:
Problem/Incident
causes MDEV-32975 Default charset doesn't work with PHP... In Review

 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/

 Comments   
Comment by Sergei Golubchik [ 2023-10-02 ]

bar, comments?

Comment by Alexander Barkov [ 2023-10-17 ]

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.

Generated at Thu Feb 08 10:30:34 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.