Uploaded image for project: 'CouchDB'
  1. CouchDB
  2. COUCHDB-549

include_docs=true doesn't honour conflicts=true

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 0.11
    • Fix Version/s: 1.0.3, 1.1, 1.2
    • Component/s: HTTP Interface
    • Labels:
      None
    • Skill Level:
      Regular Contributors Level (Easy to Medium)

      Description

      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.

        Attachments

          Activity

            People

            • Assignee:
              fdmanana Filipe Manana
              Reporter:
              candlerb Brian Candler
            • Votes:
              3 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: