Query: query filters should be properly composed on top of FromSql #16326
Assignees
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
smitpatel
added a commit
that referenced
this issue
Aug 7, 2019
This makes look up for EntityQueryable in query tree bit more complex but it adds support for providers to add custom EntityQueryable to carry more metadata as needs to and allow rest of the pipeline to be transparent about it. Current FromSql has be to converted during compilation phase since, we want to parameterize the arguments array in the methodCall. If there is nothing to parameterize then providers can directly create custom Queryable. Resolves #16326
smitpatel
added
the
closed-fixed
smitpatel
added a commit
that referenced
this issue
Aug 7, 2019
This makes look up for EntityQueryable in query tree bit more complex but it adds support for providers to add custom EntityQueryable to carry more metadata as needs to and allow rest of the pipeline to be transparent about it. Current FromSql has be to converted during compilation phase since, we want to parameterize the arguments array in the methodCall. If there is nothing to parameterize then providers can directly create custom Queryable. Resolves #16326
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently query filters are applied directly after EntityQueryable, i.e. before FromSQL call - this is unexpected, as FromSQL should be composed directly on top of EntityQueryable.
Instead, nav rewrite should detect that EntityQueryable is part of FromSQL and apply the filter after the FromSQL call
The text was updated successfully, but these errors were encountered: