Return-Path: Delivered-To: apmail-couchdb-dev-archive@www.apache.org Received: (qmail 56996 invoked from network); 6 Feb 2009 16:36:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Feb 2009 16:36:56 -0000 Received: (qmail 34306 invoked by uid 500); 6 Feb 2009 16:36:55 -0000 Delivered-To: apmail-couchdb-dev-archive@couchdb.apache.org Received: (qmail 34271 invoked by uid 500); 6 Feb 2009 16:36:55 -0000 Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@couchdb.apache.org Delivered-To: mailing list dev@couchdb.apache.org Received: (qmail 34260 invoked by uid 99); 6 Feb 2009 16:36:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2009 08:36:55 -0800 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 zachary.zolton@gmail.com designates 209.85.219.12 as permitted sender) Received: from [209.85.219.12] (HELO mail-ew0-f12.google.com) (209.85.219.12) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Feb 2009 16:36:47 +0000 Received: by ewy5 with SMTP id 5so157922ewy.11 for ; Fri, 06 Feb 2009 08:36:27 -0800 (PST) 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 :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=09I5uWfK92tm7GaYFW0F1985VPl/4pWETp7hS7KH7BA=; b=HCKv3a5HSAy+SRanzOkm8zWD8UYJf9CkM4wDjRZkmuHXqciCqIgSnXSKCVH46e8OOj 63FlgNYY49jZeV9c1Ew/pPIrUqauic/jyiBLytY9GOkhPMXpH0eVTsP3WkzG0ezZmVFL fNvW1RwVPUibOiNgMt7QBdbMsU6bcbdN1cJVs= 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:content-transfer-encoding; b=IrUXUEmYdbI4XlEf/2u/+uOeWTKnoy6qzvuNTGIr26tJsYPitjU1i55+GOZYRDLms7 3P1gJGmWouQXNehKgGMCEIMacaGYyMThpeSAA1kY/y985sRx4t/8Ga+I3DEO9zaoRHRe sDadjbJEPnXdmvhFf8nTM4ID3cApQjsA1NlLQ= MIME-Version: 1.0 Received: by 10.210.136.10 with SMTP id j10mr1458794ebd.25.1233938187190; Fri, 06 Feb 2009 08:36:27 -0800 (PST) In-Reply-To: <5e6458d0902060821u28705113r294dca237842f4ac@mail.gmail.com> References: <498464EC.1070209@diskware.net> <49859AB5.7080404@diskware.net> <5FCD4937-E8BD-4024-9E46-A24061F4D322@dionne-associates.com> <4985A930.4050802@diskware.net> <0CFB7AAD-B144-4D54-AAAD-CC96C40EB3F0@dionne-associates.com> <5e6458d0902060821u28705113r294dca237842f4ac@mail.gmail.com> Date: Fri, 6 Feb 2009 10:36:27 -0600 Message-ID: Subject: Re: couch_gen_btree: pluggable storage / tree engines From: Zachary Zolton To: dev@couchdb.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Do you think that a library of higher-order functions, for the JavaScript view layer, could be provided help codify the emerging "best practices"? I mean, we should be able to help newbies emit their keys and reduce those related documents into one object graph... On Fri, Feb 6, 2009 at 10:21 AM, Kerr Rainey wrote: >> Great question, I'd say no it runs entirely against the grain of what >> CouchDB is. Documents aren't supposed to be related to one another. But >> relational databases don't handle this kind of thing either so I figure why >> not CouchDB as it offers other features that solve lots of problems. > > I think in most practical apps that Couch targets there are > relationships between docs. The canonical Blog example has comments > that are children of a parent post. I think the emphasis on reminding > people that CouchDB is not relational tends to lead people to the > conclusion that the documents won't be related in some way. Of course > CouchDB doesn't have any built in way to specify those relationships. > > I've been playing around with conventions for specifying doc > relationships and how an app layer would make those relationships easy > to handle. It seems to be quite useful so far. It would be > interesting to see if it was possible / sensible to push some of that > further down into CouchDB. > > -- > Kerr >