[
https://issues.apache.org/jira/browse/COUCHDB-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Newson reopened COUCHDB-1141:
------------------------------------
Instead of stripping potentially valuable data posted to a document with
_deleted:true;
1) the full document body will be returned when requested. The status code will
still be 404 and the body will contain _deleted:true, either of which are
generic tests for whether a document is deleted.
2) A new view option will be added called include_deletes, allowing views to be
built out of whatever information was stored along with the deletion request.
Part 1 is not compatible with 1.0 which returns a body of {not_found:deleted}.
This must be included in the API Changes or Breaking Changes section of the
release nodes for 1.2
A separate ticket should be created to address the behavior of bulkRemove in
jquery.couch.js which does not adhere to best practices in the light of this
feature.
> Docs deleted via PUT or POST do not have contents removed.
> ----------------------------------------------------------
>
> Key: COUCHDB-1141
> URL: https://issues.apache.org/jira/browse/COUCHDB-1141
> Project: CouchDB
> Issue Type: Bug
> Components: Database Core
> Environment: All
> Reporter: Wendall Cada
> Assignee: Robert Newson
> Fix For: 1.2
>
>
> If a doc is deleted via -X DELETE, the resulting doc contains only
> id/rev_deleted:true. However, if a doc is deleted via PUT or POST, through
> adding _deleted:true, the entire contents of the doc remains stored. Even
> after compaction, the original document contents remain.
> This issue is causing databases with large docs to become bloated over time,
> as the original doc contents remain in the database even after being deleted.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
