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 akat.metin@gmail.com designates
 209.85.218.211 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=ljO/MGuO2FRqDrLDB6s7/wFTvtErHlN3em8ifhOWkBEVA1sgXKYcQZPyvguwkczpJx
         DUM1Q2qwVYrR9RLpkD5EaazsY8PH7WIwNqwRx9gWO2i8k8pK6utjcDlZOp6SnY1uXbL9
         LmNBo5YDrrn4VtSu3PVTRcFmobxK/YSxq1w+w=
MIME-Version: 1.0
In-Reply-To: <E8AFEAA8-D16D-4D4A-9D75-F1A7AAD6C0AE@apache.org>
References: <98a246a10909030535r59b1ecc2m32bfb1b0dc93fe46@mail.gmail.com>
	 <E8AFEAA8-D16D-4D4A-9D75-F1A7AAD6C0AE@apache.org>
Date: Thu, 3 Sep 2009 16:06:45 +0300
Message-ID: <98a246a10909030606q4c02cfe1id2312054bea11b04@mail.gmail.com>
Subject: Re: Tree structure: how to calculate branch node sum, using results
	from a view that calculates leaf node sums.
From: Metin Akat <akat.metin@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Well, there is a problem with this. I don't like the idea of recording
the whole path in each transaction, because it is anticipated that
accounts are able to change places in the tree. So my TRANSACTION only
holds information for only the "actual" account it's issued against,
not for its whole lineage.

On the other hand, ACCOUNTS do have the information for THEIR
path(lineage), exactly as you suggested.
So the problem now is making the connection between an account and its
balance :)


>
> query your reduce view with group_level=1 (or 2 or 3 .. depending on how
> many level you want to descend into your tree). Your "path" to the root node
> should be an array as in: ["toplevel", "firstlevel", "secondlevel"] as the
> key of your view.
>
> Cheers
> Jan
> --
>
>
>