[
https://issues.apache.org/jira/browse/COUCHDB-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12737136#action_12737136
]
Robert Burke commented on COUCHDB-441:
--------------------------------------
We could use either a generic hook to insert timestamps, or some built-in
handling where possibly the string $now$ in the JSON (possibly with a format
specifier to get ISO 8601 dates or other date formats) gets replaced with the
current UTC time.
We have many timestamps that we need to record other than just created / last
modified (when the user completed a certain workflow step, etc). We can keep a
few db machines in close enough synch with a time server. We cannot rely on
our client machines to have the correct time.
> 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.
