Return-Path: X-Original-To: apmail-couchdb-user-archive@www.apache.org Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BB9BD1057D for ; Fri, 15 Nov 2013 19:40:10 +0000 (UTC) Received: (qmail 416 invoked by uid 500); 15 Nov 2013 19:40:09 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 376 invoked by uid 500); 15 Nov 2013 19:40:09 -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 368 invoked by uid 99); 15 Nov 2013 19:40:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Nov 2013 19:40:09 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of siriele2x3@gmail.com designates 209.85.128.48 as permitted sender) Received: from [209.85.128.48] (HELO mail-qe0-f48.google.com) (209.85.128.48) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Nov 2013 19:40:05 +0000 Received: by mail-qe0-f48.google.com with SMTP id a11so2528731qen.7 for ; Fri, 15 Nov 2013 11:39:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=56Pz64JNprG8m8PvXgD17YytXBlpE5uduiBITH4NmTo=; b=VBe/gHBjyTBZlLcx5AvSiFXiw1j7hekdSjANSYkaStEDrFDf4RxDzLe6DUCfOv+1It RNFPukCkixJIgbzAk+vHc+TNoerbIIpE2LPCjLOVPSWGKLoCiZaWu+8e5e0gep/H1Klj hYEe4XoW2yoryur7+OG0arTep7o9exeXJdg99g85+HAHGKSU0GSm8ezS8FnJX+n50XmY t3QHAQXNaXtsusXIpjadiLdNxk+Hp5UXxQ11B/s4r1F0I7EIMYdt33t1FIckF6xj/Ig6 6bbOiWq30DXLlkxhNJX21/FZMonPeUsfwRaImvh3LG937K/jdB7UAybYtt6F4Sxnc/WE OdWQ== MIME-Version: 1.0 X-Received: by 10.224.89.73 with SMTP id d9mr13309437qam.5.1384544384242; Fri, 15 Nov 2013 11:39:44 -0800 (PST) Received: by 10.96.54.163 with HTTP; Fri, 15 Nov 2013 11:39:44 -0800 (PST) Received: by 10.96.54.163 with HTTP; Fri, 15 Nov 2013 11:39:44 -0800 (PST) In-Reply-To: <0EFB5ED1-8F83-46CD-9CE2-0844C2EEA3E7@mavericklabel.com> References: <0EFB5ED1-8F83-46CD-9CE2-0844C2EEA3E7@mavericklabel.com> Date: Fri, 15 Nov 2013 11:39:44 -0800 Message-ID: Subject: Re: Product management means saying no From: Stanley Iriele To: user@couchdb.apache.org Content-Type: multipart/alternative; boundary=001a11c3ce5432da5d04eb3c5cd7 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3ce5432da5d04eb3c5cd7 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable You could cleverly put that in the same view On Nov 15, 2013 11:34 AM, "Jeff Lowery" wrote: > Inline. > > > On Nov 15, 2013, at 10:51 AM, Jens Alfke wrote: > > > > > On Nov 15, 2013, at 10:03 AM, Jeff Lowery > wrote: > > > >> What I would like is the ability to specify a view that takes a > key/value map. Behind that view would be indexes for n number of k-v pai= rs > in that map in any permutation order. E.g.: > > > > A view _is_ an index. The emit() function is literally adding individua= l > key/value pairs to the generated b-tree index. If you want multiple > indexes, you create multiple views. > > You're misreading me. I know that. > > > > > It wouldn=92t be hard to write a wrapper function in your code to gener= ate > the views for the multiple permuted indexes you=92re asking for. > > I know that as well. > > > > >> I realize that the permute param results in a factorial # of views > (permuting 5 k-v pairs =3D 120 views); what is the practical limit? I as= sume > it would depend on the # of documents in a db. > > > > Yeah, this would become ridiculous pretty quickly. Especially since I= =92d > wager that most clients would only want a handful of the huge number of > indexes produced. It=92s much better to explicitly generate the indexes y= ou > need, since there is significant overhead to producing and updating them. > > And that was the point of the question. In my little problem space, I > have unordered navigation that requires lookup on each of anywhere from 1= -6 > entries. I can make this work in CouchDB, pretty much as I outlined above= . > What I asked for was the ability to specify this directly in the databas= e. > I don't have to have it, but I thought it worth posting the thought. > > > > > =97Jens > > --001a11c3ce5432da5d04eb3c5cd7--