Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: neutral (athena.apache.org: local policy)
Message-Id: <2C138B45-80F0-4041-BFA1-6A4EF69BE9CB@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: couchdb-user@incubator.apache.org
In-Reply-To: <41DF7DCF-E050-4A02-B6C6-100787592E2D@gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v929.2)
Subject: Re: partial/diff updates?
Date: Wed, 26 Nov 2008 17:34:14 -0800
References: <41DF7DCF-E050-4A02-B6C6-100787592E2D@gmail.com>


On 26 Nov 2008, at 09:57, Liam Staskawicz wrote:

> When updating a document, is there any notion of submitting a  
> partial update?  It seems like being able to specify that only some  
> subset of the fields in a document should be updated would offer  
> some efficiency benefits.  I guess I had in mind some scenario where  
> CouchDB would create the updated record by merging the existing  
> revision with the new info and saving the updated revision, but I'm  
> still new to CouchDB so I don't have a good sense of whether this  
> tramples on any important concepts.
>
> Thanks for any thoughts.

This keeps coming up. I am seeing the words "seems", "would", "some",  
"guess", "scenario", "brokeback mountain". I rather see numbers  
supporting the cause. So far, other things prove to be a bottleneck.  
I'd like to see a real app that would benefit from this. I'm not  
saying there is none, I'd just like to see it :)

Cheers
Jan
--