Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of wickedgrey@gmail.com
 designates 209.85.161.180 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=kLGp3hD/X55+liTgt2iqu1vygrJoMukQFIgR5fTLkhGB0ZS502VT7PiL3mchoF4Qim
         EmSp+2bzhPMByAVODD10qs+slTsa1B/mYG1qckgPWzEEjwRm5byBHFWdhLt9bPJ5Gw+/
         tckcUEFj+yFiTbTUu9vrJpM1z/teVtiTHprF8=
MIME-Version: 1.0
In-Reply-To: <AANLkTinhcq9gAwTPF675anGc_x37G1xJp11XQM26+iRf@mail.gmail.com>
References: <AANLkTim6PeTHYqCH+MJ+AOWXxVoYAHqOz5Hb_U8D_3yb@mail.gmail.com>
	<AANLkTik=NDhvZwAEPmF2Q0NC10WFPzLCOWevXFsVaymC@mail.gmail.com>
	<AANLkTinhcq9gAwTPF675anGc_x37G1xJp11XQM26+iRf@mail.gmail.com>
Date: Mon, 27 Sep 2010 23:34:41 -0700
Message-ID: <AANLkTikyaUS2UHWu6jAu+5hrPZcJBi7PZNfFn2FM196F@mail.gmail.com>
Subject: Re: Views with composite keys inclusive_end not functioning correctly
From: "Eli Stevens (Gmail)" <wickedgrey@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

So it was a (lack of) escaping issue, then?  :)

Eli

On Mon, Sep 27, 2010 at 9:54 PM, Danny Brain <tehdanish@gmail.com> wrote:
> Thanks Paul. I've located the real source of my problem, the actual keys
> (not example data) contained + symbols.
> These were being lost when hitting the view.
>
> On Tue, Sep 28, 2010 at 11:28 AM, Paul Davis <paul.joseph.davis@gmail.com>wrote:
>
>> On Mon, Sep 27, 2010 at 8:50 PM, Danny Brain <tehdanish@gmail.com> wrote:
>> > Hello,
>> >
>> > I'm having an issue where views with composite keys are not inclusive of
>> the
>> > endkey, even with inclusive_end specified as true.
>> > This is preventing me from correctly selecting a group of documents as
>> per
>> > the "Linked documents" section on the Http view API wiki page (
>> > http://wiki.apache.org/couchdb/Introduction_to_CouchDB_views)
>> >
>> > I'm running CouchDb 1.0.1. Example of the issue I'm seeing:
>> >
>> > composite_key_view?startkey=["AA"]&inclusive_end=true
>> > {"id":"1","key":["AA",0],"value":null},
>> > {"id":"1","key":["AA",1],"value":{"_id":"4"}},
>> > {"id":"2","key":["BB",0],"value":null}
>> >
>> > composite_key_view?startkey=["AA"]&endkey=["AA"]&inclusive_end=true
>> > No results
>>
>> ["AA"] == ["AA"] < ["AA", 0]
>>
>> >
>> > composite_key_view?startkey=["AA"]&endkey=["BB"]&inclusive_end=true
>> > {"id":"1","key":["AA",0],"value":null},
>> > {"id":"1","key":["AA",1],"value":{"_id":"4"}}
>> >
>>
>> ["AA"] < ["AA", 0] < ["AA", 1] < ["BB"] < ["BB", 0]
>>
>> > The last example works, but requires me to know what comes after AA in
>> the
>> > results, and you'd think inclusive_end would make BB show up as well.
>> > Has anyone had this problem? Any ideas on how to solve it?
>> >
>> > Thanks!
>> >
>>
>> In neither example does inclusive_end come into effect.
>>
>> To get everything with "AA" as the first element of the array key you want:
>>
>> ?startkey=["AA"]&endkey=["AA", {}]
>>
>> Inclusive end has nothing to do with it.
>>
>> HTH,
>> Paul Davis
>>
>


-- 
Eli