If I'm planning to use data caching then am I worried about conflicts while using deferred loading? It seems that I am losing control of my data with linq.
Both provide both LinqToSql and EntityFramework features (deferred loading and data caching).
For example, if you initially load a customer, then the customer will be cached and if you ask it again you will get the same example.
> If you do not load a customer's order during that initial load, then the asset allocated for that customer will be in an unloaded condition when you load those orders, then the example of the order is the property of that property. Will be available through the medium.- LinqToSql This is the first time it is used, this property will load.
- EntityFramework will load property when it is called (using the method of loading).
In both technologies, the context is a thing that caches ... so if you use more than one instance instance - you can follow different customer instances which are actually Represent the same customer in
Addressing your questions in comments. I'm talking to LinqToSql, but this stuff should also work in EntityFramework.
- This is a loading.
- Here's one.
If I stop the deferred load then I can take it that data caching will still work?
Yes, this will work, however, they are not completely independent.
- Here (this is by default)
- Here (this is by default) Read this , because it explains how these features interact.
The data cache flush is dependent on whether data and time are changing?
No flushing or cache is resetting. If you want a fresh cache, it is a matter of doing so that every instance of the datacontext has its own cache to create a new datacentax.
- There is a way to pull the cache with the changes in the update database -
- There is no way to push changes into the cache from the database.
Comments
Post a Comment