Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: error (nike.apache.org: local policy)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: [jira] [Commented] (COUCHDB-1868) Using multiple keys,
 the _all_docs built-in view acts differently then a user defined view
From: Filippo Fadda <filippo.fadda@programmazione.it>
In-Reply-To: <JIRA.12663229.1376320973936.47313.1376328047928@arcas>
Date: Mon, 12 Aug 2013 19:23:33 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <3281206B-B7A4-4299-AC92-B56E6FD7C401@programmazione.it>
References: <JIRA.12663229.1376320973936@arcas>
 <JIRA.12663229.1376320973936.47313.1376328047928@arcas>
To: dev@couchdb.apache.org

Sorry for the mess guys, I saw formatting issues so I posted using =
pastebin and I deleted the comment, adding a new one.

-Filippo

On Aug 12, 2013, at 7:20 PM, Filippo Fadda (JIRA) wrote:

>=20
>    [ =
https://issues.apache.org/jira/browse/COUCHDB-1868?page=3Dcom.atlassian.ji=
ra.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D137370=
63#comment-13737063 ]=20
>=20
> Filippo Fadda commented on COUCHDB-1868:
> ----------------------------------------
>=20
> Please look here: http://pastebin.com/rhQ5LVCW
>=20
>> Using multiple keys, the _all_docs built-in view acts differently =
then a user defined view
>> =
--------------------------------------------------------------------------=
----------------
>>=20
>>                Key: COUCHDB-1868
>>                URL: =
https://issues.apache.org/jira/browse/COUCHDB-1868
>>            Project: CouchDB
>>         Issue Type: Bug
>>         Components: View Server Support
>>           Reporter: Filippo Fadda
>>=20
>> 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=3D"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.
>=20
> --
> 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