couchdb-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Burke (JIRA)" <j...@apache.org>
Subject [jira] Commented: (COUCHDB-441) Finally implement pre-write-doc-edit handlers.
Date Thu, 30 Jul 2009 17:26:14 GMT

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

Robert Burke commented on COUCHDB-441:
--------------------------------------

Being able to insert info in docs when committed to the db implies that using PUT/POST to
create/update a document needs to return more in the response than what it currently does,
for example: {"ok":true, "id":"123BAC", "rev":"946B7D1C"}

It probably needs to return the entire JSON of the new or updated doc.  Otherwise, gotta call
the db twice.

> 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
>
>
> 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.


Mime
View raw message