On 19 Feb 2014, at 13:02 , Alexander Shorin <[email protected]> wrote:
> On Wed, Feb 19, 2014 at 3:59 PM, Jan Lehnardt <[email protected]> wrote: >> On 19 Feb 2014, at 11:42 , Alexander Shorin <[email protected]> wrote: >> >>> On Wed, Feb 19, 2014 at 2:24 PM, Robert Samuel Newson >>> <[email protected]> wrote: >>>> validate_doc_update(oldDoc, newDoc, userCtx) { >>>> >>>> if (newDoc.audit_trail[0].user != userCtx.name) { >>>> throw({forbidden: "You didn’t add your name to the audit trail!"}); >>>> } >>>> … >>>> } >>> >>> There is one issue with such approach: replications. You will not be >>> able to replicate documents which has different username in >>> audit_trail from those one who runs the replication. Or, to be more >>> detailed, you'll replicate fine all documents till the design document >>> which brings this validation function to your database and after that >>> you'll only able to store documents which matches replication's user. >> >> You could add the replication user to the validation function and keep >> the original author. > > Sure, I could. But this would be tricky and unclear for other users > that just wanted to grab the data from CouchDB. how so?
signature.asc
Description: Message signed with OpenPGP using GPGMail
