Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of newmaniese@gmail.com
 designates 74.125.83.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=VjtDZazwC69ngkvCTXIzRM4pb3IFcA0aHsoUVqZAIQ5QZUBFSrO7LjKezfZowKxX74
         3sp5bWeA0ZH+Zzc2j5TqVQmhbGR7IlBPISgLeotodwSrPRuwlsSV/198/uU5jm7GBpUJ
         WmjOf+ahN1hSXE7NwJdJg5FsPPdSIhQ8426HY=
MIME-Version: 1.0
In-Reply-To: <AANLkTik2gx=+ScrDDtHsDCOHOS96zDDf3V_-viU4w7yA@mail.gmail.com>
References: <AANLkTimh5-2qraJkLaaWON6BnEvpEs6nW4yCk_H8ZD2G@mail.gmail.com>
	<AANLkTi=cdXpj39pDB476Ch2zQmKdwVJAXhz=vWXO_oyL@mail.gmail.com>
	<AANLkTimxPthgfP6wT2J7UVb3n2Vo_rF_rZAMzH-uO_ph@mail.gmail.com>
	<AANLkTik2gx=+ScrDDtHsDCOHOS96zDDf3V_-viU4w7yA@mail.gmail.com>
Date: Fri, 5 Nov 2010 15:23:31 -0400
Message-ID: <AANLkTinsXBTnwmzq9oAz0pkWGeru=O3rubpmLD1PxGp8@mail.gmail.com>
Subject: Re: Write race conditions, working without _rev
From: Michael <newmaniese@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Very excellent. Thank you!


On Fri, Nov 5, 2010 at 1:40 PM, Mark J. Reed <markjreed@gmail.com> wrote:
> Look at update handlers.
>
> On Fri, Nov 5, 2010 at 12:44 PM, Michael <newmaniese@gmail.com> wrote:
>> On Fri, Nov 5, 2010 at 12:03 PM, Paul Davis <paul.joseph.davis@gmail.com=
> wrote:
>>>
>>> In the second case, the second person to write the document wins,
>>> erasing any changes the first write's effects. The first writer will
>>> then be in a state where his view of the database will be
>>> inconsistent. The thing his, he can't know because without requiring a
>>> _rev token he'll never get a notification of any sort of error.
>>
>> True, that is one workflow. I am not too concerned however about
>> updates trampling each other each update does not care about previous
>> revisions. This isn't people updating objects, but applications =A0To be
>> honest, I will catch the conflict and just ignore it because the data
>> then is "new enough", however if I wanted the newest data, I would
>> have to have:
>>
>> Read object to get rev
>> Try save
>> if resource conflict:
>> =A0 =A0read object for rev again
>> =A0 =A0try save
>> =A0 =A0if resource conflict:
>> =A0 =A0 =A0 =A0assume newer data and pass
>>
>> If that happens, I have 4 different hits to the database for nothing.
>> On a multithreaded server, this would happen quite frequently.
>>
>> In my workflow, the ideal situation would be to write once, without a
>> read, and for Couch to just accept the change in order.
>>
>> Is that possible?
>>
>> Thanks,
>>
>> Michael
>>
>
>
>
> --
> Mark J. Reed <markjreed@gmail.com>
>