-
Notifications
You must be signed in to change notification settings - Fork 20
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
track projection nullability through expressions #76
Comments
ygrek
added a commit
that referenced
this issue
May 6, 2022
ygrek
added a commit
that referenced
this issue
Jun 3, 2022
ygrek
added a commit
that referenced
this issue
Feb 23, 2023
ygrek
added a commit
that referenced
this issue
Nov 24, 2023
ygrek
added a commit
that referenced
this issue
Nov 24, 2023
ygrek
added a commit
that referenced
this issue
Nov 26, 2023
ygrek
added a commit
that referenced
this issue
Nov 26, 2023
ygrek
added a commit
that referenced
this issue
Nov 26, 2023
ygrek
added a commit
that referenced
this issue
Dec 1, 2023
The current state is all works as it needs besides |
I like the OP "pretty easy" claim 😹 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since we now have a basic support for NULLs I imagine it must be pretty easy to propagate information about nullability through expressions. The rules are quite simple: other than functions/operators specifically operating on nulls, everything else should be nullable if one of the operands is nullable.
NULLIF(X, Y)
is always nullableIFNULL(Xn... )
andCOALESCE(Xn...)
are nullable if every Xn is nullableIS [NOT] DISTINCT FROM
and<=>
are not nullableall (?) aggregate functions except for
COUNT()
are nullable.The text was updated successfully, but these errors were encountered: