fix(parser): distinguish MySQL constraint and index names - #2534
Open
minleejae wants to merge 1 commit into
Open
fix(parser): distinguish MySQL constraint and index names#2534minleejae wants to merge 1 commit into
minleejae wants to merge 1 commit 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
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
CONSTRAINTsymbol from the optional index nameCONSTRAINTwithout a symbol and namedUNIQUEorFOREIGN KEYindexesgetName()for the constraint symbol and expose the index name throughgetIndexName()USINGand index comments during deparsingThese cases share the same constraint/index-name ambiguity and are implemented together.
Testing
./gradlew checkFixes #1570
Fixes #538
AI assistance
OpenAI Codex assisted with the implementation and test coverage. The changes were manually reviewed and verified.