Filtering included properties about entityframework.dynamicfilters HOT 2 CLOSED

Yes, this is true. And unfortunately, there is nothing we can do about that. EF caches those objects within the DbContext and once they are there, there is no (easy) way to flush them out. The filtering we are doing applies only the sql statements.

This should only be an issue if you are changing filter values in between queries and then re-using the same DbContext. In that case, you will need to use a different DbContext. And it should only affect included properties/collections because EF populates those references from it's cache AFTER the query is executed (which is why you are probably seeing entities remaining in a child collection that should have been filtered out - they are still in the EF cache). If you query on the child DbSet directly, you will get the correctly filtered results.

from entityframework.dynamicfilters.

Really it only failed my unit tests... in production I do not re-query the
same context for entities I already have. I updated the unit test to
dispose of the dbcontext between the act and assert phases.

Yes, this is true. And unfortunately, there is nothing we can do about
that. EF caches those objects within the DbContext and once they are there,
there is no (easy) way to flush them out. The filtering we are doing
applies only the sql statements.

This should only be an issue if you are changing filter values in between
queries and then re-using the same DbContext. In that case, you will need
to use a different DbContext. And it should only affect included
properties/collections because EF populates those references from it's
cache AFTER the query is executed (which is why you are probably seeing
entities remaining in a child collection that should have been filtered out

• they are still in the EF cache). If you query on the child DbSet
  directly, you will get the correctly filtered results.

—
Reply to this email directly or view it on GitHub
#5 (comment)
.

from entityframework.dynamicfilters.