Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 simeon@simeons.net does not designate 209.85.215.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <AANLkTikgQgfvdjW7gCMD1UNd3ZBt59u1FVCWWgiHf+Mf@mail.gmail.com>
References: <AANLkTinDfNjTRbPtKQd+9cy+kBu3zt29xobZecBegKXD@mail.gmail.com>
	<AANLkTikgQgfvdjW7gCMD1UNd3ZBt59u1FVCWWgiHf+Mf@mail.gmail.com>
Date: Sat, 19 Feb 2011 11:54:04 -0800
Message-ID: <AANLkTikacUXygLaOE6Gd2iifrQq9gZrVQn1COZSyGBBw@mail.gmail.com>
Subject: Re: Query view with multiple keys with OR logic
From: "Simeon F. Willbanks" <simeon@simeons.net>
To: user@couchdb.apache.org
Cc: Robert Newson <robert.newson@gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Correct. In retrospect, I am looking for an idiom or preferred way to
achieve a dynamic view. My example states I'd like to query by
type=3D"post" OR tag=3D"tag1", but I'd like the key values to be dynamic.
My next request might be type=3D"photo" OR tag=3D"tag2". This would return
IDs 1, 2 and 3.

I understand temporary views are an option, but they aren't efficient.
Would it be best to have two permanent views which can be queried by
key and merge the results in the client? I could have one permanent
view by_type and another by_tag. This technique looks to be described
in the blog post below, but its from 2009.

http://sitr.us/2009/06/30/database-queries-the-couchdb-way.html

Thanks,
Simeon

On Sat, Feb 19, 2011 at 9:49 AM, Robert Newson <robert.newson@gmail.com> wr=
ote:
> While this;
>
> function(doc) {
> =C2=A0if (doc.type=3D=3D"post") {
> =C2=A0 =C2=A0emit(null, null);
> =C2=A0}
> =C2=A0for (var i=3D0; i<doc.tags.length; i++) {
> =C2=A0 =C2=A0if (doc.tags[i] =3D=3D "tag1") {
> =C2=A0 =C2=A0 =C2=A0emit(null, null);
> =C2=A0 =C2=A0}
> =C2=A0}
> }
>
> achieves your stated goal, I don't think it's what you're really
> asking for, right?
>
> B.
>
> On 19 February 2011 16:17, Simeon F. Willbanks <simeon@simeons.net> wrote=
:
>> Hello,
>>
>> I'm trying to fetch a set of documents with OR logic. For example,
>> fetch all documents with type=3D"post" OR tag=3D"tag1". Here are a few
>> example documents with rev omitted for brevity:
>>
>> {
>> =C2=A0 =C2=A0"_id": 1,
>> =C2=A0 =C2=A0"type": "post",
>> =C2=A0 =C2=A0"tags": [
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0"tag1",
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0"tag2"
>> =C2=A0 =C2=A0]
>> }
>>
>> {
>> =C2=A0 =C2=A0"_id": 2,
>> =C2=A0 =C2=A0"type": "photo",
>> =C2=A0 =C2=A0"tags": [
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0"tag1",
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0"tag3"
>> =C2=A0 =C2=A0]
>> }
>>
>> {
>> =C2=A0 =C2=A0"_id": 3,
>> =C2=A0 =C2=A0"type": "photo",
>> =C2=A0 =C2=A0"tags": [
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0"tag4",
>> =C2=A0 =C2=A0 =C2=A0 =C2=A0"tag5"
>> =C2=A0 =C2=A0]
>> }
>>
>> I'd like to fetch documents with the ids 1 and 2.
>>
>> It seems this method will be my starting point:
>> "A JSON structure of {"keys": ["key1", "key2", ...]} can be posted to
>> any user defined view or _all_docs to retrieve just the view rows
>> matching that set of keys. Rows are returned in the order of the keys
>> specified. Combining this feature with include_docs=3Dtrue results in
>> the so-called multi-document-fetch feature."
>> http://wiki.apache.org/couchdb/HTTP_view_API
>>
>> Am I correct so far? If yes, how would I define my map function? Would
>> I call emit multiple times and possibly use a group=3Dtrue parameter?
>>
>> Thanks,
>> Simeon
>>
>