Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Date: Tue, 8 Mar 2011 01:15:59 +0000 (UTC)
From: "Patrick Barnes (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Message-ID: 
 <149936312.3308.1299546959429.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] Commented: (COUCHDB-549) include_docs=true doesn't honour
 conflicts=true
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Patrick Barnes commented on COUCHDB-549:
----------------------------------------

This is a relevant issue to me, because I want to watch _changes for conflicted documents - and would rather avoid making an extra request for every document, just to see whether it's conflicted or not.

Ideally, any query that supports the include_docs parameter would also support any of those similar single document API parameters.

> include_docs=true doesn't honour conflicts=true
> -----------------------------------------------
>
>                 Key: COUCHDB-549
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-549
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.11
>            Reporter: Brian Candler
>            Priority: Minor
>         Attachments: couchdb-549-trunk.patch
>
>
> When you read a view and use the option 'include_docs=true' to get the source document in each result row, the option 'conflicts=true' is not honoured. You do not see a _conflicts member in the document, even if it is in a conflicting state.
> This feature request could be expanded in a couple of directions:
> 1. Make include_docs=true honour *all* options which a straightforward GET would honour - e.g. revs, revs_info, open_revs. Maybe this would be straightforward if they shared the same code path and options processing.
> 2. It has been suggested that 'conflicts=true' could be the default anyway. That is, whenever you retrieve a document, you get a _conflicts member if it is in a conflicting state, without having to ask for it. This would be unlikely to break things, but would make it less likely that conflicts would go unnoticed, and it would simplify the API a little.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira