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
Make NOT EXISTS (subquery)
and NOT IN (subquery)
more consistent in the AST
#472
Comments
I would prefer to see Exists {
expr: Box<Expr>,
subquery: Box<Query>,
} |
I guess I can help 🚀 |
@alamb but what do you mean by Maybe you mean smth like that
because we don't have any Expr::identifier in |
Yes, that is what I mean -- thank you @frolovdev |
Got your point, thanks for the clarification, here's the pr :d |
The AST has one variant to support both
IN (subquery)
andNOT IN (subquery)
:However, the variant for EXISTS does not handle
NOT EXISTS
:NOT EXISTS
is represented in the AST by wrappingExists
in aUnaryOp
withUnaryOperator::Not
.It would be nice if we could use a more consistent approach.
The text was updated successfully, but these errors were encountered: