[
https://issues.apache.org/jira/browse/COUCHDB-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426534#comment-13426534
]
Robert Newson commented on COUCHDB-1519:
----------------------------------------
So this request is better described as "Allow access to the request object in
validate_doc_update requests?"
I can't think of an objection that idea. The value of oldDoc, secObj and
userCtx are all dependent on the local database so the obvious argument at the
result of a validate_doc_update would vary when replicated is already
anticipated and irrelevant.
Can anyone see a reason not to pass the request object to validate_doc_update?
> Allow validate_doc_update.js to be aware if the update went through an update
> function before
> ---------------------------------------------------------------------------------------------
>
> Key: COUCHDB-1519
> URL: https://issues.apache.org/jira/browse/COUCHDB-1519
> Project: CouchDB
> Issue Type: New Feature
> Components: Database Core
> Affects Versions: 1.2
> Reporter: Damjan Georgievski
>
> It would be useful for the validate_doc_update function to "know" if the
> document has been processed by an update function or is sent directly to the
> DB.
> There are several possible ways to do it:
> * allow the update function to update either the userCtx or the secObj
> objects, and let that change propagate to the validate_doc_update function
> * add a completely new object that will be passed to both functions. update
> functions could then modify it.
> * add some flag to validate_doc_update parameters to signal that the document
> is direct to DB or not. But this would limit the usefulness of the feature.
> Adding special attributes to the document object, in an update function, that
> the validate function can check later, is not sufficient since that attribute
> can be sent directly to the DB also, and will be stored in the database.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
