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 north.n@gmail.com designates
 209.85.212.182 as permitted sender)
Subject: Re: any good way of filtering out your own _changes?
References: <20121003171913.02e33b2b@eee-az>
 <CAL+Y1nt3R048JJ2+GUFJyF3RRsjfkeHkkKp7f7bp9ohPFpwi7g@mail.gmail.com>
 <20121004093513.47fe9a1d@eee-az>
From: Nick North <north.n@gmail.com>
Content-Type: text/plain;
	charset=us-ascii
In-Reply-To: <20121004093513.47fe9a1d@eee-az>
Message-Id: <C1B0D0BF-D6B9-442B-A90F-05A8F4C65E20@gmail.com>
Date: Thu, 4 Oct 2012 08:10:24 +0100
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

I would go for your suggestion of including a source field in the documents.=
 If multiple instances of the app are a potential problem, then it can gener=
ate a UUID on startup and use that as the source.

Alternatively you could generate your own doc ids and include the source str=
ing in the doc id. That is probably harder as you have to make certain your d=
oc ids are unique.

Nick

On 4 Oct 2012, at 07:35, svilen <az@svilendobrev.com> wrote:

> so noone to suggest something?
>=20
>>> so i have a local db that replicates bidirectional with several
>>> others. an app uses local db, listens to _changes and also puts
>>> things sometimes. Any way to avoid it seeing it's own changes?
>=20
>>> i guess i can put a manual field e.g. "source" to *each* document or
>>> something... but that's not very neat. but may be the only way,
>>> hmmm - e.g. how to differ between different copies of same app..
>>> running in parallel.
>=20
> svil