-
Notifications
You must be signed in to change notification settings - Fork 5.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parser/parser.y: S/R conflicts 25->24. #87
Closed
Closed
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
here may be a valid syntax, for
drop column column
or abovedrop column
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AFAICT, the original grammar (before this PR) would have accepted the sentence
drop column column
as a validAlterSpecification
. The firstcolumn
instance is the optional unreservedcolumn
keyword, the secondcolumn
instance is anIdentifier
and the real name of the column to drop.That's the mess created by the keyword/identifiers mixing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"Alter table t drop column int;" is a valid sql statement but "int" is not an identifier in parser.y. @cznic
"Alter table t drop column column;" is also a valid sql statement. @siddontang
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In this way I reduce S/R conflict from 25 to 24. Is this a better way? @cznic
diff --git a/parser/parser.y b/parser/parser.y
index 8b70e02..96b6586 100644
--- a/parser/parser.y
+++ b/parser/parser.y
@@ -531,7 +531,14 @@ AlterSpecification:
Constraint: constraint,
}
}
-| "DROP" ColumnKeywordOpt ColumnName
+| "DROP" ColumnName
{
$$ = &ddl.AlterSpecification{
Action: ddl.AlterDropColumn,