I have done some research on the optimistic concurrency of entity framework and how to ensure that concurrency is dealth with. Mostly it seems that you have to set concurrencyMode=fixed on certain fields in a table, or to keep a detached object of the object being changed.
However, we make use of a once off call method that makes use of the:
using(Entity entity = new Entity())
{
}
approach. We have a singleton in the web server for our basic system but would prefer not to keep the whole entity framework in memory. However, I cannot think of a way of checking for concurrency issues without adding some time stamp to all the tables where concurrency issues can take place. This will also require us to expand our DTO's to store that time stamp.
Is there some method of handling this issue that I am not seeing?
Thanks