incubator-couchdb-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul J. Davis" <>
Subject Re: how to ignore conflicts?
Date Fri, 04 Mar 2011 02:22:16 GMT
This is where I don't mention that update handlers can do exactly what you want.

The couch way would be to write multiple docs and use a view to get the desired last value
semantics. Though sometimes there are circumstances where one might want to use some other
functionality (which clearly isn't related to update handlers doing exactly what you want
;) when the ramifications for circumventing conflict detection are understood. 

On Mar 3, 2011, at 8:19 PM, Mark Hahn <> wrote:

> I have a situation where I only want to know the latest version of a
> doc and I don't care about any older versions.  I don't care about
> conflicts.
> As far as I can tell there is no way to ignore conflicts in couch.  So
> I have to read an old version, ignore everything but the version
> value, and then save my new version.  Since this isn't atomic I have
> to check for a conflict and repeat it.  I have to do this in a number
> of places in my code.
> I was just wondering if anyone knows of a more elegant way to do this.
> Has anyone else found a need for this?

View raw message