Skip to main content

Entity Framework 4: Disable change tracking

The Entity Framework ObjectContext implements the unit of work pattern and does all the change tracking for you. However sometimes you just need to get some readonly data(for example in a CQRS architecture). In that case change tracking is just an extra performance penalty. 

How to Disable the Change Tracking Option

In Entity Framework, change tracking is being done by the ObjectStateManager. The ObjectStateManager maintains object state and identity management for entity type instances and relationship instances. In order to disable change tracking you use the MergeOption.NoTracking option of the MergeOption enumeration. Using that option will retrieve entities in a detached state.

There are 2 places where you can specify this option:

One place to disable the change tracking is when we retrieve data with the ObjectQuery object. One of the overloaded constructors of the ObjectQuery
gets as a parameter the MergeOption enumeration. 

var query = new ObjectQuery<Employee>("SELECT VALUE e FROM NorthwindEntities.Employee AS e",context,MergeOption.NoTracking);

Another place to disable the change tracking is on the EntitySet level.

context.Employee.MergeOption = MergeOption.NoTracking;

I still like the more explicit approach of the NHibernate Stateless Session more. But that’s just me…

Labels:

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...
Read more