fix(mysql): handle spaced qualified identifiers - #108
Open
Areson wants to merge 2 commits into
Open
Conversation
Co-authored-by: Codex <noreply@openai.com> Ai-assisted: true
Co-authored-by: Codex <noreply@openai.com> Ai-assisted: true
Areson
marked this pull request as ready for review
August 13, 2026 23:14
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
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.
Why
MySQL digest text can add whitespace around dots in qualified identifiers. The lexer currently splits these names into separate tokens, preventing normalized SQL and table metadata from containing the complete identifier.
What
performance_schemadigest-shaped query and long-identifier benchmarksRisk Assessment
Low — the behavior is gated to MySQL and only changes qualified names containing whitespace around a dot. Other DBMS behavior and ordinary MySQL allocation costs remain unchanged.
Validation
References