... | ... | @@ -12,9 +12,11 @@ Main issues: |
|
|
# Roadmap
|
|
|
|
|
|
* [x] [PR#13425](https://github.com/civicrm/civicrm-core/pull/13425) Warn users at installation time if their database does not support utf8mb4 - merged in CiviCRM 5.12.
|
|
|
* [ ] Change charset and collation for all core tables, custom fields, etc. [PR#13633](https://github.com/civicrm/civicrm-core/pull/13633)
|
|
|
* [ ] [PR#13633](https://github.com/civicrm/civicrm-core/pull/13633) Change charset and collation for all core tables, custom fields, etc. To be released after CiviCRM 5.12; needs testing with extensions etc.
|
|
|
* [ ] Change connection charset/collation (we set that in various places with e.g. SET NAMES) [PR#13633](https://github.com/civicrm/civicrm-core/pull/13633) [Packages PR#241](https://github.com/civicrm/civicrm-packages/pull/241) [Setup PR#16](https://github.com/civicrm/civicrm-setup/pull/16)
|
|
|
* [ ] Deal with length-related issues for varchar columns/indexes, or bump MySQL requirement to a version where that's not a problem.
|
|
|
* [ ] Figure out how to deal with extensions that might be doing string comparisons where (extension-defined) columns use different collations
|
|
|
* In [PR#13633](https://github.com/civicrm/civicrm-core/pull/13633) this is worked around by requiring innodb_large_prefix=true innodb_file_format=barracuda innodb_file_per_table=true and using ROW_FORMAT = Dynamic.
|
|
|
* [ ] Figure out how to deal with extensions that might be doing string comparisons where (extension-defined) columns use different collations.
|
|
|
* In [PR#13633] this is worked around by doing the utf8mb4 conversion on all tables in the database (similar to the utf8mb4-convert drush command).
|
|
|
|
|
|
Based on [a comment](https://chat.civicrm.org/civicrm/pl/ndckhyrueigt3q6dx8ayfez5me) by @pfigel. |
|
|
\ No newline at end of file |