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 patcito@gmail.com designates
 72.14.220.154 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:references;
        b=QtKRZ7/XREMvCnvc3G8O2ZTroVnho90A9ErZO0n86E8D4nkxRt8PzIvkvPwA4xxeSi
         FZlH49DFcRAMNocUvfLrXtuZ8yE8MkRcwfn2EIoaJcAZZkuOnx/IOyWCN/GQbk+32rGC
         ISF6daOqbDxfdy8TqbjNWHEysjpLNGVjB+c5s=
Message-ID: <6b6419750812122320i2fa3e132m6ba11bd8f734c6eb@mail.gmail.com>
Date: Sat, 13 Dec 2008 02:20:56 -0500
From: "Patrick Aljord" <patcito@gmail.com>
To: user@couchdb.apache.org
Subject: partial/diff updates?
In-Reply-To: <6b6419750812122306x22b2cfcejc9ae44b00cde6f66@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_55172_20496614.1229152856522"
References: <41DF7DCF-E050-4A02-B6C6-100787592E2D@gmail.com>
	 <492E43E1.6010501@silencegreys.com>
	 <20081127095830.GF6930@tumbolia.org>
	 <D788352E-877D-480E-81AD-18459DE121D6@gmail.com>
	 <20081127114016.GH6930@tumbolia.org>
	 <48E899BC-96E0-4528-BF65-DB0A52998E91@gmail.com>
	 <dba094300811270859n163de3d6h54070300af40b931@mail.gmail.com>
	 <492EDEAC.9010108@gmail.com>
	 <12688BCC-6141-4024-96D4-2B9B522444D7@apache.org>
	 <6b6419750812122306x22b2cfcejc9ae44b00cde6f66@mail.gmail.com>

------=_Part_55172_20496614.1229152856522
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On Thu, Nov 27, 2008 at 1:12 PM, Jan Lehnardt <jan@apache.org> wrote:

> The problem is that this would be a synthetic benchmark. I'd still very
> much like to
> see a real world application that shows in numbers that it needs partial
> updates.


Partial updates would be good in the user/group/membership situation. Right
now, I have to create a membership doc to store the user_id and group_id in
it. If I could do partial updates, I would store all the user_ids inside a
field of a group doc such as:

"memberships": [user_id1, user_id2, etc]

I could do this right now, but what if I want to update or delete a
membership? If a group has a million users, I'd need to post the whole doc
and that would definitely not scale compared to a partial update that would
just send a little diff IMO.

PS: I'm resending this mail to user@couchdb.apache.org

------=_Part_55172_20496614.1229152856522--