Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have a linq to SQL application I’m working on. I’m creating a new item, and was attempting to submit to database (insert). Once in a while, a duplicate key exception will happen, which is actually expected from time to time. The problem is that once the exception is thrown, I’m not able to insert valid items either. It keeps giving me the same error. Restarting the app solves the problem, and I’m able to insert the new values. Ideas?
If
SubmitChangesfails, all pending changes are kept for a retry. This makes it possible to catch the exception, update the objects and retry.If this is a problem, you might be keeping your DataContext for too long. I assume that you are retrying, using the same DataContext. The DataContext should be a very short-lived object, that is disposed right after
SubmitChanges.An alternative is to inspect the values returned by
DataContext.GetChangeSet()or theChangeConflictsproperty and fix the errors and retry the submit. To remove an object from the pending insert listDeleteOnSubmit()can be used.