Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 68062 invoked from network); 4 May 2009 21:10:55 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 4 May 2009 21:10:55 -0000 Received: (qmail 72648 invoked by uid 500); 4 May 2009 21:10:54 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 72565 invoked by uid 500); 4 May 2009 21:10:54 -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 72555 invoked by uid 99); 4 May 2009 21:10:53 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 21:10:53 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jchris@gmail.com designates 74.125.46.31 as permitted sender) Received: from [74.125.46.31] (HELO yw-out-2324.google.com) (74.125.46.31) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 04 May 2009 21:10:44 +0000 Received: by yw-out-2324.google.com with SMTP id 2so2137965ywt.5 for ; Mon, 04 May 2009 14:10:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type:content-transfer-encoding; bh=g3JzMojMuPgvOIyAy5erdcP8egonR6LESib5ef++3JM=; b=JrY+vNYPrTGBIEfd+FzsnZc5utpJUcIluBh7TNpy3iW7T7SY8e8pl8XpXqbRNS5Q9d EFFf7djB8jIt29skb6AiyIDkTS3ozLrnUfmDC6bBeV3NyRHk8NrQcDAvaEX12zwu834f OAlAbfYTONOAZLAb6YDbS9syf06KywK36Z3II= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type :content-transfer-encoding; b=pLeuap6AxgnMG7exAgpK01mMKQQAX9K4QrxyOx6FQrp0H6yCX64AQeTHP8vOn8K0On 6Ri5zg39L/TTBiWzhdpf9+5LnX676xP1l2KKBuWL1iRMj1OeZoeNz8fRkWp9l/60uOJO IaZ5CsUobsgPgRFkvpvEuIoOI+lKdwuAqca1w= MIME-Version: 1.0 Sender: jchris@gmail.com Received: by 10.100.132.4 with SMTP id f4mr13805260and.127.1241471423106; Mon, 04 May 2009 14:10:23 -0700 (PDT) In-Reply-To: <64a10fff0905041403k4f3cc473x7122b3bf26ba7963@mail.gmail.com> References: <7db9abd30904301802s19c742b9ya2ccb24c6acffc50@mail.gmail.com> <20090504204643.GA7083@uk.tiscali.com> <64a10fff0905041403k4f3cc473x7122b3bf26ba7963@mail.gmail.com> Date: Mon, 4 May 2009 14:10:22 -0700 X-Google-Sender-Auth: a6c33a67affff6e2 Message-ID: Subject: Re: The need for a key prefix view parameter From: Chris Anderson To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Mon, May 4, 2009 at 2:03 PM, Dean Landolt wrote: > On Mon, May 4, 2009 at 4:46 PM, Brian Candler wrote: > >> On Thu, Apr 30, 2009 at 06:02:38PM -0700, kowsik wrote: >> > Maybe just a new URL parameter for all views to query by prefix? >> > >> > _all_docs?prefix="_design/" >> >> That's basically what I was thinking of. Would also be nice to be able to >> POST {"prefixes":[...]} >> > > Why not GET or POST for ?prefix=foo&prefix=bar > Same old saw we've talked about a million times. We should add the option to do it via GET as well as POST. Multi-key is only done by POST for now because 90% of the usage would not fit in the limits of a URL length and GET doesn't tend to support request bodies. Multi prefix is the same story, and actually should be wrapped up in a generic multi-query api so we can do multiple discontinuous prefix key startkey limit endkey etc in one request. For this GET would be nice to support as well but practically useful only for the smallest cases. -- Chris Anderson http://jchrisa.net http://couch.io