incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Troy Kruthoff <>
Subject Re: deleting a deleted document
Date Thu, 10 Jul 2008 23:56:27 GMT
I would think it would be expected behavior, as the end result is the  
same regardless if the document existed.  Maybe some edge cases would  
need to know if the document was already deleted. I could be skewed  
because all of our current apps use a RDMS as a backend where deleting  
a non-existent record is no-harm-no-foul.

Another thought would be to still return success but to annotate in  
the response that the document was already deleted, or to be able to  
set an error-level as a param to bulk_docs, such as the regular  
delete:true + delete_or_error:true --something along those lines.

-- troy

On Jul 10, 2008, at 4:35 PM, Michael Hendricks wrote:

> On Wed, Jul 09, 2008 at 09:34:53PM -0600, Michael Hendricks wrote:
>> When using the bulk delete feature, I expected that deleting a  
>> document
>> which has already been deleted would respond with a 404 code.   
>> However,
>> it responds with a 201 indicating that there is no problem.  Is this
>> expected behavior?  Here are the relevant HTTP requests and  
>> responses.
>> I'm running the current trunk version of CouchDB.
> Thanks for not answering, it prompted me to send a patch instead :-)
> I sent it to the dev list.  It's only my second attempt at writing
> Erlang, but It Works For Me™
> -- 
> Michael

View raw message