[
https://issues.apache.org/jira/browse/COUCHDB-1923?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13829563#comment-13829563
]
Klaus Trainer commented on COUCHDB-1923:
----------------------------------------
Thinking about that, I just found a strong argument in favour of
[~natevw]'s original proposal to use the same query parameter name like
in the document API.
I'm wondering why we shouldn't have the functionality that is provided
by other query parameters from the document API in the view and changes
APIs as well. In fact, I see no reason why we couldn't (and shouldn't)
make the following query parameters available to be used in combination
with `include_docs`:
* attachments
* att_encoding_info
* conflicts
* deleted_conflicts
* local_seq
* meta
* revs
* revs_info
Now, thinking of that, the most sensible thing would probably be to just
stick with the names from the document API.
What do others think about that?
> Allow ?attachments=true alongside ?include_docs=true on view
> ------------------------------------------------------------
>
> Key: COUCHDB-1923
> URL: https://issues.apache.org/jira/browse/COUCHDB-1923
> Project: CouchDB
> Issue Type: Improvement
> Reporter: Nathan Vander Wilt
>
> I have a situation where it'd be handy to get inline [base64] attachments for
> the documents from a view response (already using include_docs=true).
> I wonder if this is as easy a fix as COUCHDB-549 was?
--
This message was sent by Atlassian JIRA
(v6.1#6144)
