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.

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

innodb_large_prefix is deprecated since MySQL 5.7.7 #2377

Closed
nickvergessen opened this issue Nov 28, 2016 · 1 comment
Closed

innodb_large_prefix is deprecated since MySQL 5.7.7 #2377

nickvergessen opened this issue Nov 28, 2016 · 1 comment

Comments

@nickvergessen
Copy link
Member

This setting is required for the 4-byte support: https://docs.nextcloud.com/server/11/admin_manual/maintenance/mysql_4byte_support.html

The setting was changed to be default enabled in 5.7.7 and at the same time it was deprecated: http://dev.mysql.com/doc/refman/5.7/en/innodb-parameters.html#sysvar_innodb_large_prefix

innodb_large_prefix is deprecated in MySQL 5.7.7 and will be removed in a future release. innodb_large_prefix was introduced in MySQL 5.5 to disable large index key prefixes for compatibility with earlier versions of InnoDB that do not support large index key prefixes.

I'm not sure what that means. I hope it means you simply can't control it anymore, but it remains enabled? From my understanding yes. Otherwise the experimental MySQL 4byte support is already at an end, before it started working.

Want to be sure on this, before we ship this nice stuff and then it breaks with the next MySQL major release.

cc @blizzz @LukasReschke @MorrisJobke

@blizzz
Copy link
Member

blizzz commented Nov 28, 2016

I got confirmation on IRC (#mysql on freenode) from Naktibalda that this will be basically force-enabled. Behaviour stays, switch goes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants