CODEWITHSUNDEEP
c#.netentity-frameworkobjectcontext
LukLed
LukLed

Reputation: 31842

How to refresh ObjectContext cache from db?

We are loading data from db:

var somethings = Context.SomethingSet.ToList();

Then someone deletes or adds rows outside of context. Out context still has caches deleted object, because it doesn't know they were deleted. Even if I call Context.SomethingSet.ToList(), our context still contains deleted objects and navigation properties are not correct.

What is the best method to refresh whole set from database?

Upvotes: 16

Views: 22870

Answers (3)

rnofenko
rnofenko

Reputation: 9533

For virtual properties Reload doesn't help. It needs to detach and load again

public T Reload<T>(T entity) where T : class, IEntityId
{
    ((IObjectContextAdapter)_dbContext).ObjectContext.Detach(entity);
    return _dbContext.Set<T>().FirstOrDefault(x => x.Id == entity.Id);
}

Upvotes: 1

Josh
Josh

Reputation: 44906

The Refresh method is what you are looking for:

Context.Refresh(RefreshMode.StoreWins, somethings);

Upvotes: 19

jrista
jrista

Reputation: 32960

The EF data context is an implementation of the Unit of Work pattern. As such, it is NOT designed to be keept around beyond the unit of work that is being done. Once your work is done, the expectation is that your data context is discarded.

This is a fundamental design decision for both EF v1, EF v4, and LINQ to SQL. Unless you have very specific data usage patterns and copious volumes of memory, you should avoid keeping your data contexts around longer than absolutely needed to complete your unit of work.

http://sdesmedt.wordpress.com/2009/02/18/unit-of-work-pattern/

http://takacsot.freeblog.hu/Files/martinfowler/unitOfWork.html

Upvotes: 12

Related Questions