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.
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
feat: add lambda type checking without adding lambda sql type #6966
feat: add lambda type checking without adding lambda sql type #6966
Changes from 3 commits
3ff3dca
55e968d
c034b58
1541033
6a2e65d
fd7550a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
EDIT: I see @stevenpyzhang already commented about this below, I like his suggestion! Just keeping this comment here for historical purposes
I see the following method:
What does it mean for a
SqlArgument
to have both aSqlType
and aLambdaType
? Can we update the docs to describe what this does? If it's not possible, we should enforce that in the code (make sure at most one of them isnull
).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 this is shown to users, we might want to consider
toString
on lambdas to be something like(VARCHAR, VARCHAR) -> A
instead ofLAMBDA<[VARCHAR, VARCHAR], A>
which is somewhat difficult to readThere 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.
Do you think we should leave the
LAMBDA
identifier for the newtoString
? Just wondering if users will be able to easily identify if it's((VARCHAR, VARCHAR) -> A