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: local policy)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\))
Subject: Re: commonjs in validation docs
From: =?iso-8859-1?Q?Aur=E9lien_B=E9nel?= <aurelien.benel@utt.fr>
In-Reply-To: <E701ABAA-EE68-4E40-BE09-29CE6B997BEE@gmail.com>
Date: Mon, 3 Jun 2013 09:21:40 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <6941CDA6-21FB-4A37-A275-605BFFDE4C89@utt.fr>
References: <BB4A8E0D-88F9-48B2-ADDC-D0A49EC0F097@gmail.com>
 <CAO5PmOq+Vu7rJ65+rr8xtLVi9mUyAdfiE4e_R0g8ttxPcgrd7Q@mail.gmail.com>
 <E701ABAA-EE68-4E40-BE09-29CE6B997BEE@gmail.com>
To: user@couchdb.apache.org

Hi Stephen,

> So I can't seem to get a validate_update_doc nested in a view field to =
work. =20

Why would you do that? Validations and views are completely different =
concepts.

>   "views": {
>       "validate_doc_update": "function(newdoc, olddoc, ctx, sec) =
{throw {forbidden: 'You shall not pass.'}}" // this one doesn't work

If you write this, `validate_doc_update` will be just a view. I'm pretty =
sure this is not what you want.
As a view, it should have a map and could have a reduce function, but =
would have nothing to do with validation.
=20

Regards,

Aur=E9lien