OptimisticConcurrencyException in Entity Framework

Question

0.00/5 (No votes)

See more:

Scenario:
I have some records in db for a table ProductCategory.
On one window form i have loaded the records and easily can c through navigation button. (First, Next, Previous, Last)
I have loaded a record say ID=5 on this form.
Now i go back to db and delete that record.
I can still seeing ID=5 on my form.
Now when i am trying to update this record i got OptimisticConcurrencyException.
How can i handle such scenerio in my application when there is a record on client side which has already deleted by some one else.

Thanks!

Posted 8-Apr-11 5:10am

popalzai

Add a Solution

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Wendelius · Accepted Answer · 2011-04-08T05:16:00

Solution 1

Typical solution for this is a re-fetch using the known primary key. Based on the fetch you'll either get the new row (if it's updated) or you get information that the row exists no more. You can do the re-fetch where you handle the exception.

Posted 8-Apr-11 5:16am

Wendelius

Albin Abel · Accepted Answer · 2011-04-08T06:02:00

You can use the Exists keyword at the Where clause in your update query. Here is the MSDN documentation. The example shows select, but this can be used with update as well. It checks the existence before update.

http://msdn.microsoft.com/en-us/library/ms188336.aspx[^]

Some example here as well. http://www.sqlservercurry.com/2010/02/if-row-exists-update-else-insert-in-sql.html[^]

After updates as Mika said re fetch the results, so that you will get the updated set.