This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
We are having an issue whereby if a transaction fails users are not able to "retry" to save their entity changes. In most cases we are able to prevent transaction failures from happening using application logic / validation logic. However there are some cases where we are not. For instance, some of our users have poor quality connections which can experience hiccups. If a save is attempted during one of these hiccups and the related transaction fails, EntityState is still changed to indicate that there are no pending changes. The entity (and all the users' work) basically becomes useless at that point. Can you consider Rolling back the changes to EntityState / Unit of Work that make the Entities think they have been successfully saved when a transaction fails? |
|
|
bump |
|
|
I have committed a candidate fix and it will be included in the 22 April nightly build. |
|
|
One caveat on the fix: the entity state will be set to Default if the SaveChanges succeeds, and kept unchanged otherwise. If you have some larger transaction going on, and then roll back that larger transaction *after* SaveChanges has succeeded, then the entity state will NOT be rolled back to what it was before the SaveChanges succeeded. |
|