Repository navigation
Treat INTERVAL as keyword in MySQL, TiDB and SingleStoreDB - #1000
Closed
zzoraemon043 wants to merge 1 commit into
Closed
zzoraemon043 wants to merge 1 commit into
zzoraemon043 wants to merge 1 commit into
Conversation
Author
|
duplicate of #995 |
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.
Fixes #985
INTERVALwas in both the function and keyword lists of the MySQL-like dialects. Function names win in the tokenizer and turn into plain identifiers when not followed by(, sointerval 30 dayignoredkeywordCase.It is now only a keyword there, as in MariaDB, and the shared MariaDB-like post-processing turns
INTERVALfollowed by(into a function name, the same way it already handlesSET(andVALUES(. This also makes MariaDB formatINTERVAL(5, 1, 10)as a function call instead ofINTERVAL (5, 1, 10).