-
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
Convert to Nullable in a group key throws ArgumentException (regression in 3.0-preview7) #16844
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
customer-reported
type-bug
Milestone
Comments
Need to wrap convert nodes in TranslateGroupingKey method to match types in client side code. (also necessary changes when the grouping key is used to plug into Sql tree) |
poaching. |
smitpatel
added
the
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
label
Aug 15, 2019
smitpatel
added a commit
that referenced
this issue
Aug 15, 2019
Constant/Parameter can be put in projection even if not appearing in grouping key in SQL. So now we avoid putting Constant/parameter in GROUP BY clause but treat it as normal in other places. When generating grouping key, wrap convert node to match types in initialization expression (as SQL tree ignores type nullability) Also merged leftover async group by async tests in single version. Resolves #14152 Resovles #16844
smitpatel
added a commit
that referenced
this issue
Aug 15, 2019
Constant/Parameter can be put in projection even if not appearing in grouping key in SQL. So now we avoid putting Constant/parameter in GROUP BY clause but treat it as normal in other places. When generating grouping key, wrap convert node to match types in initialization expression (as SQL tree ignores type nullability) Also merged leftover async group by async tests in single version. Resolves #14152 Resovles #16844
smitpatel
added a commit
that referenced
this issue
Aug 16, 2019
Constant/Parameter can be put in projection even if not appearing in grouping key in SQL. So now we avoid putting Constant/parameter in GROUP BY clause but treat it as normal in other places. When generating grouping key, wrap convert node to match types in initialization expression (as SQL tree ignores type nullability) Also merged leftover async group by async tests in single version. Resolves #14152 Resovles #16844
smitpatel
added a commit
that referenced
this issue
Aug 16, 2019
Constant/Parameter can be put in projection even if not appearing in grouping key in SQL. So now we avoid putting Constant/parameter in GROUP BY clause but treat it as normal in other places. When generating grouping key, wrap convert node to match types in initialization expression (as SQL tree ignores type nullability) Also merged leftover async group by async tests in single version. Resolves #14152 Resovles #16844
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.
customer-reported
type-bug
Microsoft.EntityFrameworkCore.SqlServer
version3.0.0-preview7.19362.6
The query below runs fine with EF Core
2.x
.Code to reproduce
Exception
The text was updated successfully, but these errors were encountered: