couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (COUCHDB-1850) Documentation missing view emit _id/_rev tricks for ?include_docs=true details
Date Sat, 28 Sep 2013 13:48:14 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1850?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Shorin resolved COUCHDB-1850.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.5.0
         Assignee: Alexander Shorin

Fixed in [6b6292e|https://git-wip-us.apache.org/repos/asf?p=couchdb.git;a=commit;h=6b6292e]
                
> Documentation missing view emit _id/_rev tricks for ?include_docs=true details
> ------------------------------------------------------------------------------
>
>                 Key: COUCHDB-1850
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-1850
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Documentation
>            Reporter: Nathan Vander Wilt
>            Assignee: Alexander Shorin
>             Fix For: 1.5.0
>
>
> Both the wiki and the official documentation are missing the indirect "join" fetch possible
via include_docs when the view emits *another* doc's _id e.g. http://stackoverflow.com/a/6059447/179583,
http://stackoverflow.com/a/3035522/179583, http://stackoverflow.com/a/2683228/179583 — apparently
this was only in the release notes and/or on the Couchbase blog at one time.
> Also the official documentation is missing a complete explanation of this note in the
wiki:
> "If you want to alleviate [stale view vs database inconsistency] concerns you should
emit an object with a _rev attribute as in emit(key, {"_rev": doc._rev})." — http://wiki.apache.org/couchdb/HTTP_view_API#Querying_Options
> Will this cause the old rev to be fetched? What if it's no longer available?

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

Mime
View raw message