fix: allow STATEMENT as an unquoted identifier - #2706
Merged
manticore-projects merged 1 commit intoSep 25, 2026
Merged
manticore-projects merged 1 commit into
manticore-projects merged 1 commit into
Conversation
Signed-off-by: minleejae <mmj9808@gmail.com>
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
2 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.
PostgreSQL and MySQL accept
statementas an unquoted table or column name, but JSqlParser classified STATEMENT as reserved and rejected these definitions.Move STATEMENT into the existing non-reserved keyword production so identifier parsing and lookahead helpers share the same classification. Preserve its keyword role in trigger orientation clauses.
Validation: full Gradle check and grammar ambiguity gate; CREATE/ALTER/SELECT identifier tests and a PostgreSQL FOR EACH STATEMENT trigger control. All four audited inputs pass their applicable PostgreSQL 18.6 and MySQL 9.7.2/26.7.0 execution comparisons (seven profile/input combinations).