Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of joerlend.schinstad@gmail.com
 designates 74.125.83.52 as permitted sender)
Message-ID: <4EFB9341.1090607@gmail.com>
Date: Wed, 28 Dec 2011 23:08:01 +0100
From: Jo-Erlend Schinstad <joerlend.schinstad@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:8.0) Gecko/20111124 Thunderbird/8.0
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: Modeling a tree in couchdb.
References: <4EF45C4A.5080902@gmail.com> <87zkeet1or.fsf@lifelogs.com>
In-Reply-To: <87zkeet1or.fsf@lifelogs.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Den 27. des. 2011 17:32, skrev Ted Zlatanov:
> How big is this document?  If it's like the TreeModels I've used, maybe
> you can simply keep the whole connectivity data (the edges of the graph)
> in one document, and the nodes have one document each.  That way you can
> load or update the graph in one shot; replication is simpler;
> consistency is better (at worst, a node is missing).  Renumbering is
> easier as well, since you just load a single document, rewrite it, and
> save.
>
> If this is a huge tree or you expect multiple clients to update the
> connectivity graph this is not a great solution.
>
> Ted
>
Thanks for the suggestion. Interesting idea. The problem is that I want 
this to be a general solution, which means I don't know how big it will 
be or whether it'll be accessed simultaneously by different users.

Jo-Erlend Schinstad