Modify initial migration to use acceptable max_lengths on indexed fields for MySQL utf8mb4 #162
Conversation
This file contains hidden or 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
Even though a PR was made to modify the fields for MySQL's utf8mb4 charset (max key length 191), the initial migration was still trying to create it at 255. Perhaps modifying the initial migration isn't the right way to fix this, but I'm not sure what else to do.
|
Thanks @dbreen |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Even though a PR (#116) was made to modify the fields for MySQL's utf8mb4 charset (max key length 191), the initial migration was still trying to create it at 255, which will fail. Perhaps modifying the initial migration isn't the right way to fix this, but I'm not sure what else to do.
This pertains to issue #103