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 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=hK09Uy/vskjyCvLcA+TbpKzv5HuhFLyYLOHkD5Usl9dZxyQh8G57GqK4Uab6/UKO7T
         1xMnHzlL6fOHZpFgy0uvAbGTeDcENCYFGrUKOvCPnha+tQYm+X5UKTISnO0FrHRDueyq
         NvH3Vz2zDHf4219jefpuv6htQHvFiE47XvQOQ=
MIME-Version: 1.0
In-Reply-To: <e282921e0909050020y37025b31w1925cae5018100d9@mail.gmail.com>
References: <98a246a10909030535r59b1ecc2m32bfb1b0dc93fe46@mail.gmail.com>
	 <E8AFEAA8-D16D-4D4A-9D75-F1A7AAD6C0AE@apache.org>
	 <98a246a10909030606q4c02cfe1id2312054bea11b04@mail.gmail.com>
	 <98a246a10909042334i38fbd7ccu5446ce8f7950881f@mail.gmail.com>
	 <e282921e0909050020y37025b31w1925cae5018100d9@mail.gmail.com>
Date: Sat, 5 Sep 2009 18:42:48 +0300
Message-ID: <98a246a10909050842o3a45fd8bj3eceedeb002ec522@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

On Sat, Sep 5, 2009 at 10:20 AM, Chris Anderson<jchris@apache.org> wrote:
> On Fri, Sep 4, 2009 at 11:34 PM, Metin Akat<akat.metin@gmail.com> wrote:
>> One way I can think of is to bulk update all transactions "belonging"
>> to a leaf account when moving that leaf account around.
>> I can live with having to wait some time till this gets executed.
>> Is this "bad thinking" or is it OK to some extent?
>>
>
> It can be problematic if you need ACID compliance as bulk updates
> aren't transactional. (Especially consider what can happen during
> replication.)
>
> This can often be remedied in your app model, but this is can get complex.
>

So this probably means that the least problematic way to go would be
if I calculate aggregate balances client side.
OK, for now I don't plan having millions of accounts, so I'll choose
this way after all.