Skip to content
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

[6.0] Fix to #26084 - Query: SqlExpressionFactory doesn't apply type mapping to InExpression #26153

Merged
merged 1 commit into from
Sep 27, 2021

Conversation

maumar
Copy link
Contributor

@maumar maumar commented Sep 23, 2021

We were not applying mapping to InExpression and it's constituents which could lead to failed translations when these expressions were constructed manually (e.g. as part of UDF translation)

Fixes #26084

@maumar maumar changed the title Fix to #26084 - Query: SqlExpressionFactory doesn't apply type mapping to InExpression Fix to #26084 - Query: SqlExpressionFactory doesn't apply type mapping to InExpression [6.0] Sep 23, 2021
: inExpression;
}

return item != inExpression.Item || inExpression.TypeMapping != _boolTypeMapping
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we need to do something about subquery case? Or will Select always have proper mappings? (since the ctor is not public) @smitpatel

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Select should be fine.

@ajcvickers ajcvickers changed the title Fix to #26084 - Query: SqlExpressionFactory doesn't apply type mapping to InExpression [6.0] [6.0] Fix to #26084 - Query: SqlExpressionFactory doesn't apply type mapping to InExpression Sep 23, 2021
@maumar
Copy link
Contributor Author

maumar commented Sep 27, 2021

@Pilchie for approval into 6.0 - low risk, low impact issue

@Pilchie
Copy link
Member

Pilchie commented Sep 27, 2021

Approved for EFCore 6.0

…g to InExpression

We were not applying mapping to InExpression and it's constituents which could lead to failed translations when these expressions were constructed manually (e.g. as part of UDF translation)

Fixes #26084
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Query: SqlExpressionFactory doesn't apply type mapping to InExpression
3 participants