Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-Id: <D1211EFB-61C3-4967-9BC4-A56D1CA974D8@apache.org>
From: Jan Lehnardt <jan@apache.org>
To: user@couchdb.apache.org
In-Reply-To: <ab098d450905302046y7c729004m8daa67c511ace8ba@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v930.3)
Subject: Re: Sharing code between validation functions for different views.
Date: Tue, 2 Jun 2009 14:57:47 +0200
References: <ab098d450905302046y7c729004m8daa67c511ace8ba@mail.gmail.com>


On 31 May 2009, at 05:46, macario wrote:

> I am toying with document validation and I would like not to repeat  
> the same
> validation functions on each validate_doc_update,
> I've read that validate_doc_update for each view are ran in an order  
> given
> by couchdb, so is there any way I can load some functions before the  
> whole
> validation process?

Do you mean validate_doc_update for each design document (each design
document can include multiple views). You can't run a function before  
any
one validation function. If we had a "pre_update_validate" hook, it'd  
need
guaranteed execution order and if we'd want that we could add it for  
regular
validation functions as well. As fast as sharing code, you can use  
CouchApp's*
library feature, where your code only lives in one place when you  
develop,
but gets copied when pushed to CouchDB.

* http://github.com/couchapp/couchapp

Cheers
Jan
--