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:06:07 +1100 (NCT)
From: "Paul Joseph Davis (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: <858143298.36948.1346810767778.JavaMail.jiratomcat@arcas>
In-Reply-To: <1488808466.36040.1346804947786.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (COUCHDB-1529) Add API to find the deleted
 branches of a doc's rev tree
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

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

Perhaps simpler we might just want to add a ?include_tree=true or ?revs_as_tree=true and maybe remove a couple of the other weirder options to simplify this API further.
                
> Add API to find the deleted branches of a doc's rev tree
> --------------------------------------------------------
>
>                 Key: COUCHDB-1529
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1529
>             Project: CouchDB
>          Issue Type: Improvement
>    Affects Versions: 1.2
>            Reporter: Jens Alfke
>            Priority: Minor
>
> There's no efficient way to discover the complete revision tree of a document. API options like ?open_revs=all or ?conflicts will only return active/undeleted revisions; it won't discover deleted branches resulting from already-resolved conflicts.
> There should be an extra option, like "?include_deleted=true", to use along with open_revs to tell it to return even deleted leaf revisions.

--
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