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

DOCS Adjust 4.7.0 collation docs to describe opt-in issue

Browse Source
This commit is contained in:
Garion Herman 2021-01-12 15:38:26 +13:00
parent 8438e74b08
commit aec0822e27
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 ### Default MySQL collation updated
New projects based on `silverstripe/installer` will default to the `utf8mb4_unicode_ci` collation. New projects based on Recipe 4.7.0 will default to using the `utf8mb4_unicode_ci` collation. This
This change will not affect existing projects, but developers are encouraged to adopt this collation collation provides better support for multi-byte characters such as emojis, and developers are
as it provides better support for multi-byte characters such as emojis. 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 Depending on the version of MySQL you are running, you may encounter issues with `Varchar` fields
exceeding the maximum indexable size: exceeding the maximum indexable size: