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.
The raven client (IDocumentSession) doesn’t send anything to the server until SaveChanges is called. So it could be considered as a UnitOfWork implementation, right?
Am I correct in thinking that the only difference between SaveChanges and Transaction.Commit is that the latter rolls back all changes if something failed during the commit?
If you are doing a single operation, there is no need to use an explicit transaction since the
SaveChangesresults in a implicit transaction.If you make use of
System.Transactions, you can perform multiple operations, ie multipleSaveChangesusing the same transaction. Raven will manage the transactions over http using a request header.Read more in the docs: http://ravendb.net/documentation/docs-api-transactions