tonyair/silverstripe-framework
1
0
Fork 0
mirror of https://github.com/silverstripe/silverstripe-framework synced 2024-10-22 14:05:37 +02:00
Code Issues Projects Releases Wiki Activity

Merge pull request #9821 from creative-commoners/pulls/4.7/tweak-collation-upgrade-guide

Browse Source 
DOCS Adjust 4.7.0 collation docs to describe opt-in issue
This commit is contained in:
Daniel Hensby 2021-01-12 09:34:51 +00:00 committed by GitHub
commit f7b9f3af6a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
docs/en/04_Changelogs/4.7.0.md
View File

@ -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: