-
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
Query: Deal with same querycontext parameter having multiple inferred type mapping #19503
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
priority-bug
Issues which requires API breaks and have bigger impact hence should be fixed earlier in the release
punted-for-6.0
type-bug
Milestone
Comments
Proposal: Break
|
@smitpatel Design meeting? |
ajcvickers
added
the
priority-bug
Issues which requires API breaks and have bigger impact hence should be fixed earlier in the release
label
Nov 3, 2021
smitpatel
added a commit
that referenced
this issue
Nov 8, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove Dynamic parameter/ property parameter - Obsolete TypeMappingSource from CommandBuilder - Remove obsolete code and combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
smitpatel
added a commit
that referenced
this issue
Nov 9, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove obsoleted property parameter - Obsolete Dynamic parameter - Obsolete TypeMappingSource from CommandBuilder - Remove obsolete code and combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
smitpatel
added
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
and removed
needs-design
labels
Nov 9, 2021
Didn't need breaking changes like above if we cleaned up the parameters we have atm. The design is in PR. |
smitpatel
added a commit
that referenced
this issue
Nov 20, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove obsoleted property parameter - Obsolete Dynamic parameter - Obsolete TypeMappingSource from CommandBuilder - Remove obsolete code and combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
smitpatel
added a commit
that referenced
this issue
Nov 20, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove Dynamic parameter - Obsolete TypeMappingSource from CommandBuilder - Combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
smitpatel
added a commit
that referenced
this issue
Dec 7, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove Dynamic parameter - Obsolete TypeMappingSource from CommandBuilder - Combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
smitpatel
added a commit
that referenced
this issue
Dec 7, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove Dynamic parameter - Obsolete TypeMappingSource from CommandBuilder - Combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
ghost
pushed a commit
that referenced
this issue
Dec 8, 2021
When adding parameters from query, we check if the type mapping inside TypeMapped parameter is same, if it is not then we add another parameter with different name in SQL. Clean up in relational parameter builder code - Remove Dynamic parameter - Obsolete TypeMappingSource from CommandBuilder - Combine methods which were doing same work Resolves #19503 Resolves #22524 Resolves #26472
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-query
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
priority-bug
Issues which requires API breaks and have bigger impact hence should be fixed earlier in the release
punted-for-6.0
type-bug
In above query we have only 1 query context parameter for city but in SQL, city could take different inferred type mapping. We need to determine what should we do with such cases especially if one mapping is unicode and other is not.
It also intersect with the fact that currently we have 1 to 1 mapping between query context parameters and relational parameters which we can relax and use for #17948
The text was updated successfully, but these errors were encountered: