Mailing-List: contact couchdb-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: couchdb-user@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of paul.joseph.davis@gmail.com
 designates 74.125.92.145 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:content-transfer-encoding:content-disposition
         :references;
        b=vUDuUhn7bdIGCydzODzEQ+G0FIxExxeXwKn9SkVPMhD4WS9Cqi2/zTh5b+19l9pSb6
         P23hpSMc7JTmT3nwN7M2QJOcxi6aZwffq76EK2b6976pF8bc9DolBk/6rV7oO/lkHf78
         RoawwXxEI5SXW0UmTiiO0RGBT2YyTnXhAQ3Rk=
Message-ID: <e2111bbb0811132106k29fe9ab6h7a81ed024a99b240@mail.gmail.com>
Date: Fri, 14 Nov 2008 00:06:49 -0500
From: "Paul Davis" <paul.joseph.davis@gmail.com>
To: couchdb-user@incubator.apache.org
Subject: Re: Document Updates
In-Reply-To: <F82C5745-658E-45DA-B379-625F3E47F56D@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <403828.36717.qm@web52508.mail.re2.yahoo.com>
	 <20081113220313.GG15315@tumbolia.org>
	 <E41668CB-582E-453E-96D4-F0E1C5ECE5E5@gmail.com>
	 <20081113233718.GI15315@tumbolia.org>
	 <e282921e0811131609q35c686e6r7a9440019e823d37@mail.gmail.com>
	 <0152683E-F379-46A2-B094-0315E17A407E@gmail.com>
	 <4EB51263-640C-4530-9207-9DFCF076E7D9@gmail.com>
	 <387E7267-6AC4-48FC-A680-65EA21992E9E@gmail.com>
	 <27d8d0930811132018l25566fb5rcd10d8708040e997@mail.gmail.com>
	 <F82C5745-658E-45DA-B379-625F3E47F56D@gmail.com>

The JS PATCH function is definitely an interesting idea, but I think
is not at all going to fix the issue. How many use cases are going to
be able to reduce an update operation to a function?

Most use cases that I see are of the nature: "Download JSON,
deserialize to native language, mutate, serialize, send to server".
Anyone that wants write an abstract "mutate" -> JS function thing has
props in my book.

It is forseable that you could treat it as a stored procedure though.
As in the function signature becomes "function(doc, input)" and input
is a complex JSON object that is used in the updated. This almost has
actual use in terms of the earlier thread on transaction semantics
that I assume would be implementable. But really the transaction idea
is a whole new can of worms in terms of couch would have to be allowed
to request multiple documents in one transaction etc.

I think related to Noah's original sentiment of getting some diff
system set up way outside of couch in JSON land that's implementable
in any language for anything is the best bet.

Paul

On Thu, Nov 13, 2008 at 11:53 PM, ara.t.howard <ara.t.howard@gmail.com> wrote:
>
> On Nov 13, 2008, at 9:18 PM, Ayende Rahien wrote:
>
>> Take into account that the view server is explicitly a separate
>> process.Requiring
>> it to process incoming request would create a very high overhead.
>
> i'm just saying - if people could write javascript to execute on the server
> people would really be singing hallelujah.  from my perspective it's only
> about 10000000% as cool as being to plugin a different language in as a view
> server.
>
> 2 cts.
>
>
> a @ http://codeforpeople.com/
> --
> we can deny everything, except that we have the possibility of being better.
> simply reflect on that.
> h.h. the 14th dalai lama
>
>
>
>