-
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
Sometimes SelectExpressions are pushed down unnecessarily #7766
Labels
Comments
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 3, 2017
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 3, 2017
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 3, 2017
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 7, 2017
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 8, 2017
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 8, 2017
tuespetre
added a commit
to tuespetre/EntityFramework
that referenced
this issue
Mar 8, 2017
This was largely resolved by #7843 and will be handled when #7831 is addressed (the third point about inheriting from SubQueryFromClauseFlattenrr, to be specific) cc @smitpatel |
@maumar @smitpatel @anpete should this issue be marked as closed-fixed as per the comment above? Or is it a duplicate? |
dupe of #8094 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are many cases where, for one reason or another,
LiftSubQuery
will push aSelectExpression
down into a subquery even though it is not required.Some examples:
MainFromClause
even though there are noJoinClause
s,GroupJoinClause
s, orAdditionalFromClause
sJoinClause
, aGroupJoinClause
, or anAdditionalFromClause
even though the query will not be able to be flattenedThe text was updated successfully, but these errors were encountered: