Concurrent delete and put

[Asger Hallas]

Hi,

I have a scenario where it's possible to have two processes delete and update an entity at the same time. 

Is there a way to ensure that, if an entity is deleted in the first process, it will not be reinserted upon SaveChanges() in the second process?

I would have thought that it would throw a ConcurrencyException in this situation, but despite several experiments, I can't make it do so :)

//Asger

[Itamar Syn-Hershko]

Instead of deleting mark it as deleted, this way Optimistic Concurrency will just work for you

[Asger Hallas]

Thanks for the quick reply! That makes sense. 

In my scenario the entities are sagas so there will eventually be lots and lots of documents marked as deleted. I guess that could become a problem. 

I wonder what the thoughts are behind letting a PUT succeed, when the entity does not exist in the database and the etag in the PUT commands i not Guid.Empty (when using optimistic concurrency = true of course)?

[Oren Eini (Ayende Rahien)]

I think it is a bug, I'll fix this.