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 bchesneau@gmail.com designates
 209.85.160.47 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAPNuaCgSweYwc25awH_nnjiFrEdpxsCfUP3LQzYmehh+6SSJdg@mail.gmail.com>
References: 
 <CAPNuaCgSweYwc25awH_nnjiFrEdpxsCfUP3LQzYmehh+6SSJdg@mail.gmail.com>
Date: Wed, 27 Nov 2013 09:25:09 +0100
Message-ID: 
 <CAJNb-9r7khESBFyU0pfj1p_+xiKDrjdvb5zfYbNdvAz9T_VztA@mail.gmail.com>
Subject: Re: proposed feature - list function /update handler half baby
From: Benoit Chesneau <bchesneau@gmail.com>
To: "user@couchdb.apache.org" <user@couchdb.apache.org>
Content-Type: multipart/alternative; boundary=047d7b15af4bcaca4a04ec2455d1

--047d7b15af4bcaca4a04ec2455d1
Content-Type: text/plain; charset=ISO-8859-1

On Wed, Nov 27, 2013 at 4:49 AM, Stanley Iriele <siriele2x3@gmail.com>wrote:

> Bulk updates in couchdb are a tad painful. you have to fetch them out of
> the database apply your change and save them.
>
> I propose adding the ability to have something like an update handler that
> folds across documents
>
> either in the way that lists do via get row
>
> ex.
>
> function (head, req){
>
> while (var row = getRow()){
>     row.doc.name = req.query.name;
>     send(row.doc)// except this commits the doc to disk or something here
> }
>
> or something along this line...it could return an array over the wire like
> bulk updates does....on a scale of 1 to 10 how bad of an idea is this?
>


mmm I was rather thinking to have something like :


POST /db/_bulk_update?arg1=..&...

{
  "docs" = [ doc1, ... docN ],
  "update_function": "function(doc, req) {
      ...
      return edited_doc;
  }
}


Would it works for you?

- benoit

--047d7b15af4bcaca4a04ec2455d1--