We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
IN
NOT IN
In the following on PR, I think we can move inlist related simplifier logic to `inlist_simplifier`.
Steps in inlist_simplifier
expr IN () --> false
null IN/NOT IN
or_in_list_simplifier
inlist_simplifier
expr_simplifier
In this way, when the logic grows more complex, we can easily find out related conversion about specific Expr
Originally posted by @jayzhan211 in #8949 (comment)
The text was updated successfully, but these errors were encountered:
ExprSimplifier
I am interested in this and let me try to implement it
Sorry, something went wrong.
I think this issue might be done best in multiple PRs
SO for example the first PR could just move all the inlist related simplifications into one place
Note I also have a PR to change the code, for your awareness: #8971
ok, I got it 😄
No branches or pull requests
Steps in inlist_simplifier
expr IN () --> false
,null IN/NOT IN
or_in_list_simplifier
doesinlist_simplifier
in this PR doesexpr_simplifier
In this way, when the logic grows more complex, we can easily find out related conversion about specific Expr
Originally posted by @jayzhan211 in #8949 (comment)
The text was updated successfully, but these errors were encountered: