-
Notifications
You must be signed in to change notification settings - Fork 824
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.
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
Investigate issues with utf8mb4 and MariaDB #9822
Comments
@Cheddam's comment on the previous issue:
|
Two separate problems were raised in the original issue: Collation change is opt-out in 4.7.0This will be resolved in 4.7.1, and projects using older MariaDB / MySQL versions will need to opt out manually in the meantime (and on new projects going forward.) The release notes document the most common issue that will be encountered by running the new collation against old DB versions - index size errors. Queries break in specific circumstancesThis is the challenging and as-yet-unsolved one. When running a CronTask operation, an issue was encountered where the DB would throw syntax errors on standard ORM operations. (See the stack trace in the top comment.) This syntax error suggests that the The only way we've managed to reproduce this failure is when the A similar case has been documented. However, that project was running 4.4.6, and not using the At this point we've run out of leads, so we're looking for additional information from the community. If you've faced this issue, can you please provide the following information:
Thanks! |
On MariaDB 10.x, indexes and uniques break, because MB4 takes up more bits, so 255 varchar's can't be proper indexes anymore (this is partially a bug in MariaDB not using the long indexes properly, I think) |
No further reports of any issues after upgrading, closing |
https://docs.silverstripe.org/en/4/changelogs/4.7.0/#default-mysql-collation-updated. This appears to have caused problems with installations using MariaDB. See #9811 for more discussion.
The change was accidentally made opt-out for
4.7.0
, it should be opt-in for4.7.1
once silverstripe/recipe-core#64 is merged.Stack trace from an affected server
Affected server software versions
Related code snippets
The text was updated successfully, but these errors were encountered: