Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Message-ID: <2099816975.1249241954809.JavaMail.jira@brutus>
Date: Sun, 2 Aug 2009 12:39:14 -0700 (PDT)
From: "Christopher Lenz (JIRA)" <jira@apache.org>
To: dev@couchdb.apache.org
Subject: [jira] Commented: (COUCHDB-441) Finally implement
 pre-write-doc-edit handlers.
In-Reply-To: <1046774029.1248883814797.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/COUCHDB-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12738120#action_12738120 ] 

Christopher Lenz commented on COUCHDB-441:
------------------------------------------

I think a post-save update function should be exactly analogous to the validate_doc_func feature already in CouchDB: add a function to the design doc, and have CouchDB invoke it for any document update.

In fact, this functionality could be part of the validation routine if the doc wasn't made read-only (and the function returned a new document), saving some overhead.

Am I missing something?

> Finally implement pre-write-doc-edit handlers.
> ----------------------------------------------
>
>                 Key: COUCHDB-441
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-441
>             Project: CouchDB
>          Issue Type: Improvement
>          Components: HTTP Interface
>    Affects Versions: 0.10
>            Reporter: Curt Arnold
>             Fix For: 0.10
>
>         Attachments: COUCHDB-441.patch
>
>
> It would be useful for auditing to have the identity of the user who inserted a new revision and the timestamp of the operation to be inserted in the document in the same way that the new revision number is.
> Doing this at the application level is not adequate since it would be readily spoofable and would bypass the authentication handler.
> There is a comment in couch_db:update_docs about generating new revision ids, but I couldn't quite comprehend what specific code was responsible for inserting the id into the document.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.