Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of awolff@gmail.com designates
 74.125.92.27 as permitted sender)
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=uKOU46lxw39XDRY+BG1pZQCI8Zm4ao6iDgfvdo+2JWcUZKa2C+VT5Dg1xdaV2joyI/
         8b5Cju8v297xV8fFHTsgT+0q148OLdMQO+4rgRSdG69aSX6suizzASh9VQczfIXKrdZd
         z+tgrc3dLM5ARq4azKfbBK5JFrZ8SZngtBy/Q=
MIME-Version: 1.0
In-Reply-To: <5cd531ee0907130651k2f59b926y990ba0454cec8431@mail.gmail.com>
References: <5cd531ee0907130651k2f59b926y990ba0454cec8431@mail.gmail.com>
Date: Mon, 13 Jul 2009 07:55:34 -0700
Message-ID: <e8d26ac40907130755i3b65de33u66ec0782d96b4a24@mail.gmail.com>
Subject: Re: DAGs (directed acyclic graphs) in couchdb
From: Adam Wolff <awolff@gmail.com>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=00163646d6dc9e4470046e97834a

--00163646d6dc9e4470046e97834a
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

There didn't turn out to be a good solution, that I found at least. In our
app, we're just storing a reference to the root node and putting the DAG
together on the client side.
A

On Mon, Jul 13, 2009 at 6:51 AM, Jason Sachs <jmsachs@gmail.com> wrote:

> This thread (
> http://mail-archives.apache.org/mod_mbox/couchdb-user/200812.mbox/%3Ce8d26ac40812120812l43046a3i7754c9b2bdcac764@mail.gmail.com%3E
> )
> mentioned directed acyclic graphs briefly... but if there was a moment
> of enlightenment on good ways to represent DAGs in couchdb, I must
> have missed it. Any thoughts? I've read the hierarchy page on the wiki
> (http://wiki.apache.org/couchdb/How_to_store_hierarchical_data) but it
> requires each node to store its materialized path. DAGs don't have a
> single unique path to nodes, and even if you tweaked this design to
> list the multiple paths to a node from the root (or from a designated
> root, since a DAG doesn't really have the concept of a root, and can
> have multiple roots), you still have the possibility of combinatorial
> explosions of data.
>

--00163646d6dc9e4470046e97834a--