Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DOCS Adjust 4.7.0 collation docs to describe opt-in issue #9821

Merged
merged 1 commit into from
Jan 12, 2021
Merged

DOCS Adjust 4.7.0 collation docs to describe opt-in issue #9821

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 8 additions & 3 deletions docs/en/04_Changelogs/4.7.0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down