incubator-couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexander Shorin (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (COUCHDB-1519) Allow validate_doc_update.js to be aware if the update went through an update function before
Date Tue, 02 Jul 2013 00:27:20 GMT

     [ https://issues.apache.org/jira/browse/COUCHDB-1519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alexander Shorin updated COUCHDB-1519:
--------------------------------------

    Component/s:     (was: Database Core)
                 View Server Support
    
> 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: View Server Support
>    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
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message