You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@couchdb.apache.org by "Ryszard Szopa (JIRA)" <ji...@apache.org> on 2008/06/14 23:09:45 UTC
[jira] Created: (COUCHDB-79) it shouldn't be possible to delete
documents that don't exist in a bulk upload
it shouldn't be possible to delete documents that don't exist in a bulk upload
------------------------------------------------------------------------------
Key: COUCHDB-79
URL: https://issues.apache.org/jira/browse/COUCHDB-79
Project: CouchDB
Issue Type: Bug
Components: HTTP Interface
Reporter: Ryszard Szopa
Priority: Minor
If you try to delete in _bulk_docs (by setting the attribute "_deleted" to true) a document that doesn't exist (either because it doesn't have an id, or because it has an id not present in the database), CouchDB replies with a happy 201 (created). This is not a good behavior: if I am trying to delete something that's not in the database, then I am probably doing something wrong, and I'd like to know it: the whole transaction (bulk upload) should fail.
Also, the present behavior is inconsistent with respect to deleting with a DELETE request, which returns a 404.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (COUCHDB-79) it shouldn't be possible to delete
documents that don't exist in a bulk upload
Posted by "Jan Lehnardt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12605104#action_12605104 ]
Jan Lehnardt commented on COUCHDB-79:
-------------------------------------
Re: "either because it doesn't have an id, or because it has an id not present in the database" <- in CouchDB's case this is synonymous. If something exists in a database it has an id.
In general I think we agreed on behaving _bulk_docs like a proper transaction and if a DELETE causes an error, the transaction should be aborted. We also agreed on introducing the old behaviour with an optional member (_ignore_errors or so) that allows fire-and-forget type of bulk requests. This might be relevant to this discussion.
> it shouldn't be possible to delete documents that don't exist in a bulk upload
> ------------------------------------------------------------------------------
>
> Key: COUCHDB-79
> URL: https://issues.apache.org/jira/browse/COUCHDB-79
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 0.8
> Reporter: Ryszard Szopa
> Priority: Minor
>
> If you try to delete in _bulk_docs (by setting the attribute "_deleted" to true) a document that doesn't exist (either because it doesn't have an id, or because it has an id not present in the database), CouchDB replies with a happy 201 (created). This is not a good behavior: if I am trying to delete something that's not in the database, then I am probably doing something wrong, and I'd like to know it: the whole transaction (bulk upload) should fail.
> Also, the present behavior is inconsistent with respect to deleting with a DELETE request, which returns a 404.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (COUCHDB-79) it shouldn't be possible to delete
documents that don't exist in a bulk upload
Posted by "Ryszard Szopa (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/COUCHDB-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ryszard Szopa updated COUCHDB-79:
---------------------------------
Affects Version/s: 0.8
> it shouldn't be possible to delete documents that don't exist in a bulk upload
> ------------------------------------------------------------------------------
>
> Key: COUCHDB-79
> URL: https://issues.apache.org/jira/browse/COUCHDB-79
> Project: CouchDB
> Issue Type: Bug
> Components: HTTP Interface
> Affects Versions: 0.8
> Reporter: Ryszard Szopa
> Priority: Minor
>
> If you try to delete in _bulk_docs (by setting the attribute "_deleted" to true) a document that doesn't exist (either because it doesn't have an id, or because it has an id not present in the database), CouchDB replies with a happy 201 (created). This is not a good behavior: if I am trying to delete something that's not in the database, then I am probably doing something wrong, and I'd like to know it: the whole transaction (bulk upload) should fail.
> Also, the present behavior is inconsistent with respect to deleting with a DELETE request, which returns a 404.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.