From user-return-12962-apmail-couchdb-user-archive=couchdb.apache.org@couchdb.apache.org Tue Sep 28 01:10:46 2010 Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 33480 invoked from network); 28 Sep 2010 01:10:46 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 28 Sep 2010 01:10:46 -0000 Received: (qmail 81270 invoked by uid 500); 28 Sep 2010 01:10:45 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 81217 invoked by uid 500); 28 Sep 2010 01:10:44 -0000 Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@couchdb.apache.org Delivered-To: mailing list user@couchdb.apache.org Received: (qmail 81209 invoked by uid 99); 28 Sep 2010 01:10:44 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Sep 2010 01:10:44 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of tehdanish@gmail.com designates 74.125.82.54 as permitted sender) Received: from [74.125.82.54] (HELO mail-ww0-f54.google.com) (74.125.82.54) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 28 Sep 2010 01:10:36 +0000 Received: by wwi18 with SMTP id 18so864wwi.23 for ; Mon, 27 Sep 2010 18:10:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=o6afrWXQw5i+HPNwh+yPbzKZRUa0jsc/2EgZZ4tpjwI=; b=Vh+t8u8efgDsWEdbLD9LsDXTrgRm1ea+cC+dRsTw2PifehegP84FNQ//YScuu0YsKT Xkaf3A9///f1n5q0Gc76S7hZ5kBoPWKI8FA4P1lftrgvuh1F1HUXXh0OXogJHqhuMdKK XxgHzlXaRG/sP6kf7Gf0CvVYxN1C0N24i46fs= 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=kNKLz4gBV4SsIKw0ApVv2Cm0svTBqS3lLrZYtpgh3NJDQ1oQ5qy1iZ4P4+RdyayJZM NcIhov7blajhk1twC/dxxo35Gqp7i3mTalkSSQQSAWk8SPZ/6pTA3qbjwgegdll8jR5+ r1/oRErpWPHS9lZvoaJhm+V2I4NguZuHrn/kA= MIME-Version: 1.0 Received: by 10.216.155.206 with SMTP id j56mr6923825wek.67.1285635779464; Mon, 27 Sep 2010 18:02:59 -0700 (PDT) Received: by 10.216.71.200 with HTTP; Mon, 27 Sep 2010 18:02:59 -0700 (PDT) In-Reply-To: References: Date: Tue, 28 Sep 2010 11:02:59 +1000 Message-ID: Subject: Re: Views with composite keys inclusive_end not functioning correctly From: Danny Brain To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=0016363ba3e2f2103004914767c2 X-Virus-Checked: Checked by ClamAV on apache.org --0016363ba3e2f2103004914767c2 Content-Type: text/plain; charset=UTF-8 Hi Eli, Thanks heaps for the fast response! I've tried this unsuccessfully previously, and just tried again to verify. composite_key_view?startkey=["AA"]&endkey=["AA",{}]&inclusive_end=true No results On Tue, Sep 28, 2010 at 10:55 AM, Eli Stevens (Gmail) wrote: > I *think* that instead of using inclusive_end, you want to have > endkey=["AA", {}] . > > The {} is considered to come after all other key values. > > Per my understanding, inclusive_end is for when you know *exactly* > what key you want to stop on. > > Eli > > On Mon, Sep 27, 2010 at 5:50 PM, Danny Brain 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 > > > > 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"}} > > > > 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! > > > > > > -- > Eli > --0016363ba3e2f2103004914767c2--