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 faust451@gmail.com designates
 209.85.221.184 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:content-transfer-encoding;
        b=ZxqYYZU/oTaxX2ZgT8r7R4wI6Q8TS7pA9dVJmwei8Ks8sVYepnh6navwQgDAMu5eO4
         eyE1i4Y56842clHjOJIHl04LaGiLTWaqRkDXECAA6HyXvDWxrrOMBhH2uadowq5U9M9c
         yCM6VU+udotXlHn+rmzZ5c4xrG7HOjFh1sHwM=
MIME-Version: 1.0
In-Reply-To: <n2yccb631ed1004081031g63097337g303d01c661114865@mail.gmail.com>
References: <y2qf39928a61004080820h27b3c95boc14ee5f418ff483e@mail.gmail.com>
	 <q2jf728979f1004080928gfc32027fm1749fa86eb665ad4@mail.gmail.com>
	 <s2lf39928a61004081029l23b6a489p425ac027e48b3f07@mail.gmail.com>
	 <n2yccb631ed1004081031g63097337g303d01c661114865@mail.gmail.com>
Date: Thu, 8 Apr 2010 21:53:48 +0400
Message-ID: <m2sf39928a61004081053i28a62256z76aec696f25417fb@mail.gmail.com>
Subject: Re: About denormalization and keep consistent
From: faust 1111 <faust451@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

What difference?
if do
Author
  after_save
     if name_changed?
        Content.by_author(self).each {|content|
           content.author_name =3D self.name;
           content.save(bulk=3Dtrue)
       }

or i start backend process to track Author _changes.

This code not guarantee that all contents will updated.


2010/4/8 Andrew Melo <andrew.melo@gmail.com>:
> On Thu, Apr 8, 2010 at 12:29 PM, faust 1111 <faust451@gmail.com> wrote:
>> I can catch changes in my app before save author, may be backend
>> process is surplus in my case.
>> i need consistent, when i update author name i must know that all
>> contents with author was updated success.
>
> Then their suggestion of watching _changes works for you. Start
> watching _changes. Make all your changes to the documents' authors.
> Any changes that come through on _changes, make sure they have the
> proper author. Keep watching _changes until you're sure that nobody
> has stale data they're waiting submit.
>
>
>>
>>
>> 2010/4/8 Zachary Zolton <zachary.zolton@gmail.com>:
>>> I suggest you check out the _changes API:
>>> http://books.couchdb.org/relax/reference/change-notifications
>>>
>>> Basically, if you have doc types A & B, where B maintains a denormed
>>> bit of A, then you can watch the _changes feed in a backend process.
>>> When an A gets updated, hit a view of all B's related to that
>>> particular A, and update the dernomed data.
>>>
>>> On Thu, Apr 8, 2010 at 10:20 AM, faust 1111 <faust451@gmail.com> wrote:
>>>> Hi guy's
>>>> I return back to my problem with denormalization.
>>>>
>>>> is it possible to keep consistent when apply denormalization?
>>>> For example
>>>> Content
>>>> =A0 have author (we store author name and id in Content)
>>>>
>>>> When author name changed(that's happens not frequently)
>>>> i need find all content belong to this author and update author name
>>>> but what if this operation not finished (not all docs was updated)
>>>>
>>>> What i can do in this case?
>>>> Thanks.
>>>>
>>>
>>
>
>
>
> --
> --
> Andrew Melo
>