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 ben2004uk@googlemail.com
 designates 74.125.82.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=u+VenwnyKtpzZ7zRJFg/MTLm5S6jQw8dObo3Niixp3a1csO8LHFx2rhZ/9GtkhRh2B
         9zzXpkogToOfBjDMHOm43p2X3uREtP3elDy2nMiqnY6t4OtxNJQkufaiPmLZEI37+dcD
         y0GaaeEL5yIFuF1p67Bd3Wj/NVFWU6qjglBeM=
MIME-Version: 1.0
Date: Sun, 4 Apr 2010 23:57:32 +0100
Message-ID: <k2ga04554c01004041557ka0815b94r1571dc36a5f2663e@mail.gmail.com>
Subject: Replication Filters: When changing restrictions data becomes out of
	sync
From: Ben Hall <ben2004uk@googlemail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

I have the following setup:

MainDB
FirstDB
SecondDB

First and Second will contain a subset of the data in MainDB. I
planned to use Replication Filters to populate the DB.  This is
working great, until I change a document in MainDB from being
restricted to FirstDB to being restricted to SecondDB.

When this happens, replication correctly applies it to SecondDB -
however it still exists in FirstDB. As such, my data is now
inconsistent.

Is this correct? The only thing I can think is that I'm going to have
to manually delete the document from FirstDB - which is a little bit
annoying.

Is there a better way?

Thanks

Ben
http://twitter.com/Ben_Hall