[MDEV-25291] Add support for missing MySQL collations Created: 2021-03-29  Updated: 2022-06-19

Status: Open
Project: MariaDB Server
Component/s: Character Sets
Fix Version/s: None

Type: Task Priority: Major
Reporter: Ian Gilfillan Assignee: Unassigned
Resolution: Unresolved Votes: 2
Labels: Compatibility

Issue Links:
Duplicate
duplicates MDEV-20772 Missing collations after upgrade to 10.4 Closed
Relates
relates to MDEV-7495 GB18030 Open

 Description   

MySQL 8 supports a number of collations that MariaDB doesn't. MariaDB doesn't support the gb18030 charset (MDEV-7495) , but there are also numerous unsupported utf8mb4 collations that MariaDB should support:

gb18030_bin
gb18030_chinese_ci
gb18030_unicode_520_ci
utf8mb4_0900_ai_ci
utf8mb4_0900_as_ci
utf8mb4_0900_as_cs
utf8mb4_0900_bin
utf8mb4_cs_0900_ai_ci
utf8mb4_cs_0900_as_cs
utf8mb4_da_0900_ai_ci
utf8mb4_da_0900_as_cs
utf8mb4_de_pb_0900_ai_ci
utf8mb4_de_pb_0900_as_cs
utf8mb4_eo_0900_ai_ci
utf8mb4_eo_0900_as_cs
utf8mb4_es_0900_ai_ci
utf8mb4_es_0900_as_cs
utf8mb4_es_trad_0900_ai_ci
utf8mb4_es_trad_0900_as_cs
utf8mb4_et_0900_ai_ci
utf8mb4_et_0900_as_cs
utf8mb4_hr_0900_ai_ci
utf8mb4_hr_0900_as_cs
utf8mb4_hu_0900_ai_ci
utf8mb4_hu_0900_as_cs
utf8mb4_is_0900_ai_ci
utf8mb4_is_0900_as_cs
utf8mb4_ja_0900_as_cs
utf8mb4_ja_0900_as_cs_ks
utf8mb4_la_0900_ai_ci
utf8mb4_la_0900_as_cs
utf8mb4_lt_0900_ai_ci
utf8mb4_lt_0900_as_cs
utf8mb4_lv_0900_ai_ci
utf8mb4_lv_0900_as_cs
utf8mb4_pl_0900_ai_ci
utf8mb4_pl_0900_as_cs
utf8mb4_ro_0900_ai_ci
utf8mb4_ro_0900_as_cs
utf8mb4_ru_0900_ai_ci
utf8mb4_ru_0900_as_cs
utf8mb4_sk_0900_ai_ci
utf8mb4_sk_0900_as_cs
utf8mb4_sl_0900_ai_ci
utf8mb4_sl_0900_as_cs
utf8mb4_sv_0900_ai_ci
utf8mb4_sv_0900_as_cs
utf8mb4_tr_0900_ai_ci
utf8mb4_vi_0900_ai_ci
utf8mb4_vi_0900_as_cs
utf8mb4_zh_0900_as_cs

 Comments   
Comment by Jean [ 2022-06-19 ]

I wish this would get resolved, it's a major problem for me and I seem to have found no work-around to it
I basically need utf8mb4_0900_as_ci so when I SELECT a table where COLUMN = "Warrior" for example, then "WÂRRÏOR" wouldn't be considered, but "WARRIOR" would.

I guess I'll need to use something else than MariaDB

Generated at Thu Feb 08 09:36:35 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.