Entity framework Optimistic Concurrency Exception

Question

Should I maintain a Timestamp property on my Model classes for enable optimistic concurrency for data update and delete ? If I won't use such a attribute,whether EF will give concurrency exception at run time or not ?

Is this must for enable the concurrency handling ?

[Timestamp]
public byte[] RowVersion { get; set; }

Shimmy Weitzhandler · Accepted Answer · 2015-04-19 02:31:05Z

11

Yes, either that or you decorate a property with [ConcurencyCheck]. Otherwise you will end up with scenario last write wins.

EDIT:

Official tutorial on how to handle Concurrency:

Handling Concurrency with the Entity Framework in an ASP.NET MVC Application

edited Apr 19, 2015 at 2:31

Shimmy Weitzhandler

105k127 gold badges437 silver badges646 bronze badges

answered Sep 21, 2013 at 8:03

Admir Tuzović

11.2k7 gold badges38 silver badges75 bronze badges

Sign up to request clarification or add additional context in comments.

2 Comments

Sampath Over a year ago

Can you say the must be needed situation for handle concurrency issues (I mean some examples)?

Admir Tuzović Over a year ago

Yes you must use either [TimeStamp] or [ConcurrencyCheck]. Then you need to decide how would you deal with Concurrency. Warn user? Reload from database and merge? I've added a tutorial in post for you which has extensive explanation.

Collectives™ on Stack Overflow

Entity framework Optimistic Concurrency Exception

1 Answer 1

2 Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

2 Comments

Your Answer

Sign up or log in

Post as a guest

Related