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 ryan.mohr@gmail.com designates
 209.85.212.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAL+Y1nuvVeps0btwTUpQ_13UG9Udp868iadctEHTG1E--Da6MA@mail.gmail.com>
References: 
 <CALrOv66xW-PoSYcCjGVP=+Epw87dYCo=ZuxV_UgMG2G1Qs3oiQ@mail.gmail.com>
	<CAPNuaCjT+baW-6XQjR9arV=NxGbo1=UmWaMuZ2Xkvno78+oJPQ@mail.gmail.com>
	<CABvT1DHHXweMJhdoGet8UgBu3S-DCLhU2-1X3pC6QaVQC2+QPA@mail.gmail.com>
	<CALJb-KH4kmOL4Vak1zEoBVyiZFBe7OEduR3G0BoLhSFsAOsPdw@mail.gmail.com>
	<EE86A26B-AC01-402D-84D8-12C40D88C467@couchbase.com>
	<D352B0AE7EF2D844A6296C8C30F948E01EE3688C@lv-exmbx01.ad.agi>
	<CABvT1DHWwMj+gw59MF0NcVKCJ4Do_0Hqv4zizxi76Ezm+b+prA@mail.gmail.com>
	<CADJQ9xJNddMf85eASb4Ooq0nQhxD2aZJRdg8K6vv9QNu3sAt1A@mail.gmail.com>
	<CAOA1H+Kcrvjy_bxnR4E1rr2Yn85gsPFjdtjukk+gfQw9Sgi7KA@mail.gmail.com>
	<F98BD807-64FF-457B-BDCD-06DDFC83681E@couchbase.com>
	<CAOA1H++-xBw5UAav=mDT2Nbi2KJ_nBKq1RKBTfVRVz6QXR3Qmg@mail.gmail.com>
	<CAL+Y1nuvVeps0btwTUpQ_13UG9Udp868iadctEHTG1E--Da6MA@mail.gmail.com>
Date: Sun, 10 Nov 2013 13:47:31 -1000
Message-ID: 
 <CAOA1H+LpuZYB5rb5-SsumbBgVuJAw6z9Xs5g1KjDqHyrBM4P3Q@mail.gmail.com>
Subject: Re: overwrite document without revision?
From: Ryan Mohr <ryan.mohr@gmail.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=001a11c38424256a5004eadb3d8a

--001a11c38424256a5004eadb3d8a
Content-Type: text/plain; charset=ISO-8859-1

Dave, this isn't my thread. Alex had asked:

> Is there any way to unconditionally overwrite a document without
first making a round-trip to get the current rev?

Everyone said no. Looks like it's totally doable using new_edits=false and
a script that resolves any conflicts by simply picking the most recent
update.

Whether or not couchdb is a good fit for Alex's needs is a separate issue.

On Sunday, November 10, 2013, Dave Cottlehuber wrote:

> Hi Ryan,
>
> You're desperately trying to find a way to make CouchDB's immutable
> storage system work like a mutable one. Please don't :-) -- it's going
> against the grain.
>
> I'd suggest taking a step back for a moment, reading carefully through
> these 2 sections in particular from the guide:
>
> http://guide.couchdb.org/draft/consistency.html
> http://guide.couchdb.org/draft/conflicts.html
>
> What features are you after from your overall app that makes couchdb a
> good fit (or not)?
>
> What Jens is referring to is that new_edits is an API that allows the
> multi-master replication engine to introduce conflicts directly into
> the existing revision tree for a document. You'll then need to resolve
> these introduced conflicts directly to ensure that your new entry
> "comes out on top" as there's no guarantees it won't by default.
>
> A+
> Dave
>
>

--001a11c38424256a5004eadb3d8a--