This repository has been archived by the owner on May 28, 2019. It is now read-only.
do fix up of tables first with ROW_FORMAT=DYNAMIC #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
infojunkie
added a commit
that referenced
this pull request
Dec 5, 2015
do fix up of tables first with ROW_FORMAT=DYNAMIC
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As described in [1] a table's row format must be either ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED in order for the "innodb_large_prefix=1" setting to have any effect.
Quote:
For InnoDB tables that use COMPRESSED or DYNAMIC row format, you can enable the innodb_large_prefix option to allow index key prefixes longer than 767 bytes (up to 3072 bytes). Creating such tables also requires the option values innodb_file_format=barracuda and innodb_file_per_table=true.) In this case, enabling the innodb_large_prefix option would allow you to index a maximum of 1024 or 768 characters for utf8 or utf8mb4 columns, respectively. For related information, see Section 14.5.7, “Limits on InnoDB Tables”.
[1] https://dev.mysql.com/doc/refman/5.6/en/charset-unicode-upgrading.html