Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of tehdanish@gmail.com designates
 74.125.82.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=j2kg3e+GSSdGpnORAYlnA0YILYphuHPVgSZGQk9H9hOnwShMTnD+vE4Cpl80rBCrXI
         YHuaP8HNduMRGTVHFvk+JBm1tkHVT2gEER3IN4uScA5XEdUs+OvnZ8UDhAwVlDm97r8o
         cMxFVMMAxAGnE9kXEHc6iopg6PAd12ZiHEu48=
MIME-Version: 1.0
In-Reply-To: <AANLkTikyaUS2UHWu6jAu+5hrPZcJBi7PZNfFn2FM196F@mail.gmail.com>
References: <AANLkTim6PeTHYqCH+MJ+AOWXxVoYAHqOz5Hb_U8D_3yb@mail.gmail.com>
	<AANLkTik=NDhvZwAEPmF2Q0NC10WFPzLCOWevXFsVaymC@mail.gmail.com>
	<AANLkTinhcq9gAwTPF675anGc_x37G1xJp11XQM26+iRf@mail.gmail.com>
	<AANLkTikyaUS2UHWu6jAu+5hrPZcJBi7PZNfFn2FM196F@mail.gmail.com>
Date: Tue, 28 Sep 2010 16:39:51 +1000
Message-ID: <AANLkTinpvDECugqWBwwfO7LwOTOoFL5FcyVv2MnZ+Ucg@mail.gmail.com>
Subject: Re: Views with composite keys inclusive_end not functioning correctly
From: Danny Brain <tehdanish@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=0016364c7367b3ac9204914c1c47

--0016364c7367b3ac9204914c1c47
Content-Type: text/plain; charset=UTF-8

That's the one.
For some reason the startkey was handled fine (without being escaped
correctly), but the endkey was grumpy.

On Tue, Sep 28, 2010 at 4:34 PM, Eli Stevens (Gmail)
<wickedgrey@gmail.com>wrote:

> 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
>

--0016364c7367b3ac9204914c1c47--