-
Notifications
You must be signed in to change notification settings - Fork 489
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
wip:*: Support sytax of reset placement options
#1353
Conversation
[REVIEW NOTIFICATION] This pull request has not been approved. To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
how can we split “default” (policy name) with default (keyword)? or we just support SET DEFAULT syntax? |
reset db placement options
clear db placement options
clear db placement options
reset db placement options
ctx.WriteKeyWord("DEFAULT") | ||
} else { | ||
ctx.WriteName(n.StrValue) | ||
} |
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.
if you want 'DEFAULT'
and DEFAULT
to be distinguishable you should create a separate PlacementOptionType
. playing tricks in Restore() won't do much.
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.
We also want to make `DEFAULT`(identifier) differs from DEFAULT (keyword) 🤣, does it work?
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.
yes. "DEFAULT"
in parser.y always refer to the keyword. since DEFAULT
is a reserved keyword it shouldn't collide with Identifier
.
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.
Sounds great to me, I will try it.😆
reset db placement options
reset db placement options
reset db placement options
reset placement options
merged to pingcap/tidb#28463 by pingcap/tidb#28257 |
What problem does this PR solve?
Issue Number: pingcap/tidb#18203
related to pingcap/tidb#18203
What is changed and how it works?
Check List
Tests
Code changes
Side effects
Related changes