[jira] Commented: (COUCHDB-549) include_docs=true doesn't honour conflicts=true

["Jens Alfke (JIRA)" <ji...@apache.org>]

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

Jens Alfke commented on COUCHDB-549:
------------------------------------

This actually goes back to 0.10.0.
>From some historical evidence (a unit test in the CouchObjC library that used to work but now breaks) it looks like this changed sometime after 0.8.

Is this considered a bug to be fixed, or just a design limitation?

> 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
>
> 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.
-
You can reply to this email to add a comment to the issue online.