From aec0822e275d3ceacdcfb303d09cb9b1798480ef Mon Sep 17 00:00:00 2001 From: Garion Herman Date: Tue, 12 Jan 2021 15:38:26 +1300 Subject: [PATCH] DOCS Adjust 4.7.0 collation docs to describe opt-in issue --- docs/en/04_Changelogs/4.7.0.md | 11 ++++++++--- 1 file changed, 8 insertions(+), 3 deletions(-) diff --git a/docs/en/04_Changelogs/4.7.0.md b/docs/en/04_Changelogs/4.7.0.md index 53eadf7ad..5e15db976 100644 --- a/docs/en/04_Changelogs/4.7.0.md +++ b/docs/en/04_Changelogs/4.7.0.md @@ -86,9 +86,14 @@ If you'd rather retain the previous YAML parser for the time being, you can run ### Default MySQL collation updated -New projects based on `silverstripe/installer` will default to the `utf8mb4_unicode_ci` collation. -This change will not affect existing projects, but developers are encouraged to adopt this collation -as it provides better support for multi-byte characters such as emojis. +New projects based on Recipe 4.7.0 will default to using the `utf8mb4_unicode_ci` collation. This +collation provides better support for multi-byte characters such as emojis, and developers are +encouraged to adopt this collation across all projects where possible. + +When upgrading to Recipe 4.7.0, this configuration change will also incorrectly apply to existing +projects. _This is unintended_, and in Recipe 4.7.1 and later the change will be opt-in. If you +wish to opt out of the new collation during an upgrade to Recipe 4.7.0, remove the +`app/_config/database.yml` configuration file that is added during the Composer update process. Depending on the version of MySQL you are running, you may encounter issues with `Varchar` fields exceeding the maximum indexable size: