Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-ID: <40746.82.73.244.17.1264351048.squirrel@webmail.claranet.nl>
Date: Sun, 24 Jan 2010 17:37:28 +0100 (CET)
Subject: Re: Revisions for Created Documents
From: "Markus Jelsma" <markus@buyways.nl>
To: <user@couchdb.apache.org>
In-Reply-To: <97552DEE-5559-4DA4-80EA-E3F9B4861300@me.com>
References: <97552DEE-5559-4DA4-80EA-E3F9B4861300@me.com>
Importance: Normal
Reply-To: markus@buyways.nl
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit

Hi Mike,


This is not completely watertight, especially considering replicating over
documents. In general, all new documents are prefixed with 1- but you can
just as easily add a document and set the _rev manually to a number higher
than 1. Setting _rev to 0 won't do the trick though.

If your scenario doesn't allow for these kind of `features`, you could use
it i guess.


Cheers,

Michael Beam said:
> Hi There,
>
> My application is monitoring the _changes API to update its UI for
> updated documents. I would also like to take actions in my app for new
> documents, so I wanted to get the list's opinion on detecting created
> documents.
>
> Is checking the revision string for the prefix "1-" is a reliable and
> robust method of recognizing a change as a new document?  Everything in
> my experience points to yes, but I may be overlooking some subtleties
> about how that all works.
>
> Thanks!
>
> Mike Beam