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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #5989.
MySQL and MariaDB silently drop an index prefix length that equals the indexed column's length (
KEY idx (col(20))on aVARCHAR(20)comes back asKEY idx (col)), so a table declared with such a length keeps producing a drop/create diff against its introspected version, forever. Following the direction discussed in #5976, the MySQLComparatornow anticipates this during normalization: a prefix length equal to the column's length is treated as no length. Effective prefixes (shorter than the column) are untouched, composite indexes only lose the lengths that MySQL would drop, and primary keys are left as is. Same normalization family as the recent float-default phantom-diff fix.