Return-Path: Delivered-To: apmail-couchdb-user-archive@www.apache.org Received: (qmail 13049 invoked from network); 28 Oct 2009 13:10:57 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Oct 2009 13:10:57 -0000 Received: (qmail 87350 invoked by uid 500); 28 Oct 2009 13:10:55 -0000 Delivered-To: apmail-couchdb-user-archive@couchdb.apache.org Received: (qmail 87255 invoked by uid 500); 28 Oct 2009 13:10:55 -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 87244 invoked by uid 99); 28 Oct 2009 13:10:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2009 13:10:55 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com designates 209.85.211.186 as permitted sender) Received: from [209.85.211.186] (HELO mail-yw0-f186.google.com) (209.85.211.186) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Oct 2009 13:10:50 +0000 Received: by ywh16 with SMTP id 16so658652ywh.13 for ; Wed, 28 Oct 2009 06:10:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=+xK6NobqVtXP485z9joNx+n5YpyV+kQAqUfH9fr77mk=; b=c967P0WP9kBDBIjeHjk4/bwie6wtRpn74saFxyyDxJiRqkWElu3gKNAICmlL5bwBLK ixpHawEd6BAU+e77Ol06Tamyl4+79x1VkHGl4Cas0xJIwUFHzr3HxaoBF0z3XmxK0Wvq XFa4MIrSBhtUAMvqDpaQb7PF+DJdCoBIZP8Yg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=ZjsbvXyMNqXxMhAieZFXwRbsu7jgMHi2vFN/epKX7z1UL+lihCsSKuM/OPnI/eI87b b5WSctyq8yT99eQhVALjMd6cI2t600nqr2HrklLOm21Hl6blBMa8hynMUNvEqfeqprZi 00SN06SRnrehnlnkVY+p8E4SNtGhel5EqeRd0= MIME-Version: 1.0 Received: by 10.101.72.16 with SMTP id z16mr21032ank.90.1256735429072; Wed, 28 Oct 2009 06:10:29 -0700 (PDT) In-Reply-To: <319C03F7A120754B9128CF308BF5E0370308FF08@nasa-dtw-ex004.nasa.cpwr.corp> References: <319C03F7A120754B9128CF308BF5E0370308FF08@nasa-dtw-ex004.nasa.cpwr.corp> From: Paul Davis Date: Wed, 28 Oct 2009 09:10:09 -0400 Message-ID: Subject: Re: Can you connect one view to another? To: user@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Matt, In short, no. In long, also no, but it can be done server side by persisting view results into a new db and running the subsequent Map/Reduce on the derived database. Rinse. Repeat. Admittedly that's not the most elegant solution and requires server side logic, but as it turns out, the cascading is difficult to accomplish with the current incremental view system. HTH, Paul Davis On Wed, Oct 28, 2009 at 8:43 AM, Welch, Matt wro= te: > I'm pretty new to CouchDB so please pardon me if this is a silly > question, but can you connect the results of one view to another? > > Imagine I have a bunch of children documents and each child has a > favorite color. I also have a bunch of toy documents and each toy has a > color. I want to build a list of what toys each child will like based on > its color. > > I can make a view to emit(color, name) for each toy and something > similar for each child. But then do I have to connect the two in my > code? If your dataset gets large that seems like a lot of work gets > pushed out to the client end. Is there any way to construct a view that > links these together? > > > > > The contents of this e-mail are intended for the named addressee only. It= contains information that may be confidential. Unless you are the named ad= dressee or an authorized designee, you may not copy or use it, or disclose = it to anyone else. If you received it in error please notify us immediately= and then destroy it. > >