-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Null semantics applies incorrectly for SqlFunction #16245
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
It does not seem like duplicate. Do you think #16078 would be fixed by doing something unrelated to null semantics? |
@smitpatel you are right, its a bug, fix incoming |
maumar
added a commit
that referenced
this issue
Jun 26, 2019
problem was that when we were computing a nullability of sql function, if the function didn't have instance, we would inherit nullability from the expression that was visited previously. Fix is to only use nullability of instance expression if that expression is not null.
maumar
added a commit
that referenced
this issue
Jun 26, 2019
problem was that when we were computing a nullability of sql function, if the function didn't have instance, we would inherit nullability from the expression that was visited previously. Fix is to only use nullability of instance expression if that expression is not null.
maumar
added a commit
that referenced
this issue
Jun 26, 2019
problem was that when we were computing a nullability of sql function, if the function didn't have instance, we would inherit nullability from the expression that was visited previously. Fix is to only use nullability of instance expression if that expression is not null.
smitpatel
pushed a commit
that referenced
this issue
Jun 28, 2019
problem was that when we were computing a nullability of sql function, if the function didn't have instance, we would inherit nullability from the expression that was visited previously. Fix is to only use nullability of instance expression if that expression is not null.
smitpatel
pushed a commit
that referenced
this issue
Jun 28, 2019
problem was that when we were computing a nullability of sql function, if the function didn't have instance, we would inherit nullability from the expression that was visited previously. Fix is to only use nullability of instance expression if that expression is not null.
smitpatel
pushed a commit
that referenced
this issue
Jun 28, 2019
problem was that when we were computing a nullability of sql function, if the function didn't have instance, we would inherit nullability from the expression that was visited previously. Fix is to only use nullability of instance expression if that expression is not null.
Fixed via #16266 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Not sure if it would be applicable to more types but we generate this SQL,
Where_string_to_upper
[c].[CustomerID]
is never null since its PK and metadata is also correctly says that.Null semantics is ending up with stale value.
Found out when I made totally unrelated change which made value of stale value change and generated correct SQL.
The text was updated successfully, but these errors were encountered: