-
Notifications
You must be signed in to change notification settings - Fork 605
Resolved bug in parse_function_arg
#1826
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
Open
LucaCappelletti94
wants to merge
2
commits into
apache:main
Choose a base branch
from
LucaCappelletti94:func-int-bug
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
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 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
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
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.
Oh how did you mean here by
Int2
in this example not being parsed as a custom datatype, do we get back a different type or doesparse_data_type
fail in that scenario?I think ideally we will want to do without this
self.peek_token()
to avoid the cloning that it includesThere 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.
The argument named
Int2
(as described in the issue) is not parsed asDataType::Custom
, but as aDataType::Int2
. Analogously, any other such argument names that collides with data types from other SQL engines would be parsed into a type.Now, if I were to convert back to string
DataType::Int2
I would get some arbitrary capitalization which in this case isINT2
- without thepeek_token
, I am unsure how we can preserve the initial token from being lost.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.
Ah I see that makes sense! Maybe something like this we can do to restrict the cloning to only when necessary?
Coming to think about it, would we not need to sanity check that the first token is actually a
Token::Word
variant? current code seems to assume that to be the case which might not necessarily be true.For example following how the following sql would be parsed, we can probably have a test case it
we would call
to_string()
on only the first token which would bestruct
even though this query is technically invalid?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.
Could you provide a complete example of such a broken case, so that I may add it to the test suite?
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.
I think something like this potentially