19fa2275ac
MariaDB 11.5 has introduced changes to default collation, switching to uca1400_ai_ci from general_ci [1] With that they've also introduced changes to default value of character-set-collations value, which now has precedence over collation-server/collation-connection if CHARSET is supplied in request leading to potential conflicts [3] when performing migrations. We introduce set of new variables to be able to control and potentially switch to new collation/charsets by default in the future, while enabling us to keep current behavior. [1] https://mariadb.com/docs/release-notes/community-server/old-releases/release-notes-mariadb-11-5-rolling-releases/what-is-mariadb-115#other [2] https://mariadb.com/docs/server/server-management/variables-and-modes/server-system-variables#character_set_collations [3] https://jira.mariadb.org/browse/MDEV-37544 Related-Bug: #2121797 Change-Id: I5adcd1f2d5160410fb9ded8e7f967e9773434e35 Signed-off-by: Dmitriy Rabotyagov <dmitriy.rabotyagov@cleura.com>
12 lines
297 B
YAML
12 lines
297 B
YAML
---
|
|
features:
|
|
- |
|
|
Added new variables to control MariaDB default charset and collation:
|
|
|
|
* galera_default_charset
|
|
* galera_default_collation
|
|
* galera_default_collation_set
|
|
|
|
Variable ``galera_default_collation_set`` is defined in my.cnf only for
|
|
MariaDB versions >= 11.5.
|