[
https://issues.apache.org/jira/browse/COUCHDB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13737160#comment-13737160
]
Filippo Fadda commented on COUCHDB-1868:
----------------------------------------
1) Agree 100%.
2) Sure.
3) _all_docs seems easy to fix, I took a look at the code.
4) I totally agree with you, that's the way we should go.
I'll be glad to contribute and make a patch but I need support, at least to
know parts and functions to look after and to answer my noob questions. This
could me my first contribute to the core and since I really need it done for my
project, I'll be glad to work on it. You are gonna probably spend more time
supporting me than doing the patch yourself, but you'll earn a new contributor.
;-)
> Using multiple keys, the _all_docs built-in view acts differently then a user
> defined view
> ------------------------------------------------------------------------------------------
>
> Key: COUCHDB-1868
> URL: https://issues.apache.org/jira/browse/COUCHDB-1868
> Project: CouchDB
> Issue Type: Bug
> Components: View Server Support
> Reporter: Filippo Fadda
>
> When you query a view using multiple keys, the _all_docs built-in view acts
> differently then a user defined view:
> 1) in the first case CouchDB returns "not_found" for every not found key;
> 2) querying a user defined view produces, instead, an empty array.
> In the first case you obtain error="not_found" for every key, when you query
> a user defined view you simply don't get any rows, just the total rows for
> the view.
> See: http://pastebin.com/D7NExJrd
> Now, regarding 'keys' the documentation says something like: "Used to
> retrieve just the view rows matching that set of keys. Rows are returned in
> the order of the specified keys."
> In a normal case, CouchDB should return just a row for each matched key, but
> it will really help, having an option to return a row for every key, even
> there if not found, because it's more easy, cycle through results.
> Let's suppose the application I'm doing gets the last 30 blog posts,
> displaying for each one, information that are stored into related documents.
> The application will query, using as keys the posts' identifiers, other views
> to get, for example, if a post has been starred from the current logged-in
> user, etc.
> If a view always returns a number of rows equals to the number of keys, the
> application can cycle from 0 to 29 and display all the related information
> for a post.
--
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
