couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jan Lehnardt <>
Subject Re: overwrite on update if _rev not latest?
Date Wed, 13 May 2009 11:40:59 GMT

On 12 May 2009, at 09:28, Michael Stillwell wrote:

> Is there any way to get CouchDB to overwrite a document (instead of
> generating a conflict) when updating an existing document with a _rev
> that does not match the latest _rev?
> One simple use case for this is that of a user opening up two user
> profile tabs on a website, then editing both, and submitting both.
> The second "update" will fail--is there a way to force this through?
> (I don't particularly care if the second update clobbers some changes
> from the first.)

This goes against CouchDB's core design philosophy, so it is unlikely
that we'll ever get this feature.

I don't understand enough of you use case (how do "profiles" match
documents et al). With a doc per profile, you don't get any write  


View raw message