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 robert.newson@gmail.com
 designates 209.85.214.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=bKbVrAb93FYhXphaH1nwvPKqAWhBADR2juNfTkrXFPQQlwQwDr5ZLa22t2as6WMoMS
         S6DTcsjPXzchn0r6i1x9ubiHMrbwd4+cv8qEpeIFPOeP6w+2aj7yrlg3jZSjLn8bO2Zm
         eNSfbr/YhP7kNb8fsMZut3AoBYys4g70Dt2ao=
MIME-Version: 1.0
In-Reply-To: <4D508749.2080806@databill.com>
References: <4D507F64.7030405@databill.com>
	<8117E686-BE57-4003-BB56-B9F4C2EA954D@rowanshire.net>
	<4D508749.2080806@databill.com>
Date: Tue, 8 Feb 2011 00:01:22 +0000
Message-ID: <AANLkTikg2Tf=6eCZdg=Q=PQsvUm3UJ19WVvyjNyuhNdQ@mail.gmail.com>
Subject: Re: Atomic update of multiple attachments?
From: Robert Newson <robert.newson@gmail.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

You could also use the COPY feature. :)

On Mon, Feb 7, 2011 at 11:59 PM, Wayne Conrad <wayne@databill.com> wrote:
> Bob, One of my needs is that requestors can get the most recent "complete=
"
> set of attachments, even while a new set is being assembled. =A0I've no s=
ense
> of what it takes to work with previous version of a document, esp. since =
(as
> I understand it) replication doesn't transfer old revisions of documents.
> =A0Do you think your idea can be made to work with this need?
>
> I'm wondering if something can be done that's similar to how we
> create/rename files in Unix. =A0Can I create a temporary document, load i=
t up
> with attachments, and then rename it?
>
> Wayne
>
> On 02/07/11 16:38, Robert Johnson wrote:
>>
>> Create your document with attributes "eventual_attachment _count" (set
>> this to the expected count) and "attachment_count_so_far" (set this to
>> zero).
>> As you add each attachment, increment "attachment_count_so_far"
>>
>> Create a view which only emits when "attachment_count_so_far" =3D
>> "eventual_attachment _count"
>>
>>
>> For update:-
>>
>> Remove docs and decrement "attachment_count_so_far"
>> Reset "eventual_attachment _count"if necessary
>> Add new attachments and increment "attachment_count_so_far"
>>
>> Does this work for you?
>>
>> Bob
>>
>> On 7 Feb 2011, at 23:25, Wayne Conrad wrote:
>>
>>> Is there anything I can do to achieve the illusion of atomic update of =
a
>>> set of attachments? =A0Here's the effect I'd like:
>>>
>>> For create:
>>> 1. Create a document.
>>> 2. Add attachments to it.
>>> 3. Only now does the document and all of its attachments become visible=
.
>>>
>>> For update:
>>> 1. Delete all of the document's attachments.
>>> 2. Add a new set of attachments to the document.
>>> 3. Only now does the new set of attachments appear to replace the old.
>>>
>>> I'm using Couchdb 1.0.2 and CouchRest 1.0.1. =A0I'm not opposed to chea=
ting
>>> to achieve my goal. =A0Suggestions of "Did you think of doing this-othe=
r-thing
>>> instead?" are also welcome.
>>
>
>