Hi,
I just noticed that the MemoryCacheManager implementation of ICacheManager is registered in Autofac as an InstancePerHttpRequest. What's the reason behind this choice? I would have thought it would be a SingleInstance.
ICacheManager in Autofac as InstancePerHttpRequest?
- 126
- 1860
- 4/15/2011
- Canada
Andrei,
I noticed that this modification causes some issues as the cached entities are still considered attached to their original DbContext. If you set a reference to them in another object graph, the following error occurs:
An entity object cannot be referenced by multiple instances of IEntityChangeTracker.
In this case, the referenced object can be reloaded using the id from the cached object before being assigned in the new object graph. I think that even if we detach the object from the DbContext before cahing it, once we assign it to another object graph it will automatically attach to the other DbContext and the same problem will occur.
I noticed that this modification causes some issues as the cached entities are still considered attached to their original DbContext. If you set a reference to them in another object graph, the following error occurs:
An entity object cannot be referenced by multiple instances of IEntityChangeTracker.
In this case, the referenced object can be reloaded using the id from the cached object before being assigned in the new object graph. I think that even if we detach the object from the DbContext before cahing it, once we assign it to another object graph it will automatically attach to the other DbContext and the same problem will occur.
Team Member
- 16626
- 156015
- 10/22/2008
- Armenia
Yes, it's old issue. And that's why all entities are not cached between requests. Find more info here.
But MemoryCacheManager caches only locales and settings. But we don't pass these entities to appropriate services when updating.
But MemoryCacheManager caches only locales and settings. But we don't pass these entities to appropriate services when updating.