[
https://issues.apache.org/jira/browse/COUCHDB-523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12927982#action_12927982
]
Paul Joseph Davis commented on COUCHDB-523:
-------------------------------------------
I would say that Adam's array based approach is probably going to be more
sensible as it allows people to more easily control the order in which the
queries are processed in the case where someone wants to aggregate some sort of
result across the multiple views.
For the response I think having a {"results": $array_of_results} wrapper is
probably better as it allows for future changes more easily if we start
annotating that response.
Just for fun, has anyone considered how this would integrate with _lists? Or if
we people should be allowed to make queries on multiple views, and if so if
they should or shouldn't be scoped to a design doc?
> View API POST keys to retrieve multiple docs by key could also allow for
> multiple 'range' queries, i.e. an array of { startkey: .., endkey: ... }
> params in the POST
> --------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: COUCHDB-523
> URL: https://issues.apache.org/jira/browse/COUCHDB-523
> Project: CouchDB
> Issue Type: Improvement
> Components: HTTP Interface
> Reporter: Nathan Stott
> Assignee: Adam Kocoloski
> Priority: Minor
> Fix For: 1.1
>
> Attachments: couch_httpd_view.erl, multi_start_end_key.diff,
> ranged_key_post.diff
>
>
> It would be useful if I could do a single POST to a view to retrieve multiple
> ranges specified by startkey, endkey.
> The format could be as follows:
> { "ranges": [ { "startkey": "a", "endkey": "c" }, { "startkey":"g",
> "endkey":"z" } ] }
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
