Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Wed, 5 Sep 2012 13:08:07 +1100 (NCT)
From: "Paul Joseph Davis (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <128204950.36951.1346810887629.JavaMail.jiratomcat@arcas>
In-Reply-To: <1544984512.36179.1346805198228.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (COUCHDB-1530) Add a mode to _all_docs to
 include deleted docs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-1530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448395#comment-13448395 ] 

Paul Joseph Davis commented on COUCHDB-1530:
--------------------------------------------

+1 for include_deleted. Though I'll note that this won't allow for an efficient view of *only* deleted docs. Perhaps a view option like local seqs or including design docs that allows users to create views would be a good addition as well.
                
> Add a mode to _all_docs to include deleted docs
> -----------------------------------------------
>
>                 Key: COUCHDB-1530
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1530
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Jens Alfke
>            Priority: Minor
>
> There's currently no efficient way to discover the deleted documents in a database, since _all_docs only returns active documents. It can be useful to show all documents, even deleted ones, for troubleshooting or forensic purposes.
> I propose adding an option like "?include_deleted=true" to _all_docs that will cause it to return deleted documents as well. To provide a way to tell deleted docs apart from active ones (if the include_docs option isn't on), the "value" object should include a "deleted":true property for those docs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira