draft: investigate MariaDB utf8mb4_uca1400_ai_ci collation handling#4435
Draft
mujib77 wants to merge 2 commits into
Draft
draft: investigate MariaDB utf8mb4_uca1400_ai_ci collation handling#4435mujib77 wants to merge 2 commits into
mujib77 wants to merge 2 commits into
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.
Summary
This draft PR documents investigation work related to MariaDB collation issue #4222.
What I investigated
Reproduced the issue on current
mainCreated a minimal MariaDB reproduction schema
Traced parsing flow into
internal/engine/dolphin/parse.goInvestigated the
p.pingcap.Parse(...)parser entrypointAttempted a temporary normalization workaround for:
Current status
The attempted workaround did not fully resolve the issue and also caused parser-related test failures.
At the moment, it appears the unsupported collation handling likely occurs deeper in the parser / DDL validation layer.
Opening this draft PR mainly to share investigation findings and make future debugging easier.