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

Adam Kocoloski commented on COUCHDB-549:
----------------------------------------

I'm +1 on both directions outlined by Brian.

Patrick, a possible alternative in the case of _changes is to perform the query 
with ?style=all_docs, which will cause all leaf revisions (the winning one and 
all conflicts) to show up in the row.  It doesn't discriminate between 
unresolved and resolved/deleted conflicts, but you could push a filter function 
to to suppress the deleted conflicts if you wanted.

> 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

Reply via email to