Andrius Juozapaitis schrieb:
Sven: This solution would simply throw an exception from spring DAO layer if the object you're trying to update is already being modified by another thread, before even accessing couch - so no need to rollback the intermediate state. Couchdb would also throw exception, if you're trying to modify using an old revision number, as usual.
But isn't this was already happens? If you try to update a document with a non-current _rev value, jcouchdb will throw an UpdateConflictException. The only thing that has changed is that you now need to check if all your documents went through if you're using bulk transactions.
Regards, Sven Helmberger
