Re: failed commit not totaly rolled back

>>Why is there "post-commit processing" ? shouldn't all processing be part of the
>>transaction such that if any parts fail, the whole thing gets rolled back?
>>
>>
>Because after the commit has succeded in the repository, the working copy
>must be updated to reflect the actual revisions stored there. That's not
>part of the server transaction
>
>

Because of this, the server should never respond with an error if the
transaction was commited!

This happened to me some weeks ago: It was a very large commit, I went
to the fsfs transaction directory to see it "live" while it was being
built =). The commit was succesful, but subversion failed to delete the
txn directory (as I was standing in that dir with a shell). The client
received an error, and the WC was left broken. IMO these "cleanup
errors" should be logged in the server, but the operation must still be
reported as succesful to the client...!

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 18 21:04:35 2005