-
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: Select.Include.OrderBy ignores the include #10101
Comments
workaround is to apply Include after the order by |
Problem was that in QueryOptimizer, if we flattened redundant subquery (Include result operator was the only element on that subquery and we strip those out) we did not update PathFromQuerySource on the IncludeResultOperator annotations with the new Qsre. Also, in nav rewrite we were trying to match PathFromQuerySource with regular comparison, rather than using ExpressionComparer.
Problem was that in QueryOptimizer, if we flattened redundant subquery (Include result operator was the only element on that subquery and we strip those out) we did not update PathFromQuerySource on the IncludeResultOperator annotations with the new Qsre. Also, in nav rewrite we were trying to match PathFromQuerySource with regular comparison, rather than using ExpressionComparer.
Problem was that in QueryOptimizer, if we flattened redundant subquery (Include result operator was the only element on that subquery and we strip those out) we did not update PathFromQuerySource on the IncludeResultOperator annotations with the new Qsre. Also, in nav rewrite we were trying to match PathFromQuerySource with regular comparison, rather than using ExpressionComparer.
Problem was that in QueryOptimizer, if we flattened redundant subquery (Include result operator was the only element on that subquery and we strip those out) we did not update PathFromQuerySource on the IncludeResultOperator annotations with the new Qsre. Also, in nav rewrite we were trying to match PathFromQuerySource with regular comparison, rather than using ExpressionComparer.
Problem was that in QueryOptimizer, if we flattened redundant subquery (Include result operator was the only element on that subquery and we strip those out) we did not update PathFromQuerySource on the IncludeResultOperator annotations with the new Qsre. Also, in nav rewrite we were trying to match PathFromQuerySource with regular comparison, rather than using ExpressionComparer.
fixed by d527800 |
…ion projection doesn't work Problem was that we were not properly updating PathFromQuerySource and QuerySource properties on IncludeResultOperator when processing SelectMany in nav rewrite. This issue is similar to #10101
…ion projection doesn't work Problem was that we were not properly updating PathFromQuerySource and QuerySource properties on IncludeResultOperator when processing SelectMany in nav rewrite. This issue is similar to #10101
…ion projection doesn't work Problem was that we were not properly updating PathFromQuerySource and QuerySource properties on IncludeResultOperator when processing SelectMany in nav rewrite. This issue is similar to #10101
Something strange happens to me, at first run (request) warning is there, then everything is silent, EF core 2.2.3, contextLifetime and optionsLifetime are scoped, the warning reapers one time once app is restarted. |
@MarcelChirtes This is expected. The query compiles once, at which time you see the warning, and is then cached for future calls. |
@ajcvickers fair point, I assume there's no way to suppress it? Thank you. |
@MarcelChirtes Any warning can be suppressed using |
If OrderBy is present, we ignore the include, if it is absent then we do include correctly
The text was updated successfully, but these errors were encountered: