[
https://issues.apache.org/jira/browse/COUCHDB-1141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13025514#comment-13025514
]
Randall Leeds commented on COUCHDB-1141:
----------------------------------------
That looks like a fix to me.
I wonder if we should make some macros for element/2 in places where we have
tuples like this. Doing it as a macro would mean that it'd still expand to
something suitable for a guard but it scares me how easy it is to typo an index
and screw everything up.
> 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
