This question is locked. New answers and comments are not allowed.
Hello,
I was just curious if the process of saving changes to the database via Context.SaveChanges() was similar to EF, which can be a huge black hole when an error occurs (since it doesn't tell you which entity received an error, and only commits some of the changes unless a transaction was used). Does OpenAccess work the same way, where you call SaveChanges, and it tries to push up all the objects, and you may or may not get an error? Or does it open up what's going on within the submitted entities to let you know which object caused an error.
I understand transactions exist to prevent that partial update, and I'm in full agreement, however I was wondering if there were ways to tap into it anyway.
Thanks.
I was just curious if the process of saving changes to the database via Context.SaveChanges() was similar to EF, which can be a huge black hole when an error occurs (since it doesn't tell you which entity received an error, and only commits some of the changes unless a transaction was used). Does OpenAccess work the same way, where you call SaveChanges, and it tries to push up all the objects, and you may or may not get an error? Or does it open up what's going on within the submitted entities to let you know which object caused an error.
I understand transactions exist to prevent that partial update, and I'm in full agreement, however I was wondering if there were ways to tap into it anyway.
Thanks.