So it was a (lack of) escaping issue, then? :) Eli
On Mon, Sep 27, 2010 at 9:54 PM, Danny Brain <[email protected]> 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 > <[email protected]>wrote: > >> On Mon, Sep 27, 2010 at 8:50 PM, Danny Brain <[email protected]> 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
