You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@couchdb.apache.org by Suraj Kumar <su...@inmobi.com> on 2014/02/13 14:09:44 UTC
Changes API with user details
Hi,
Is it possible to get which user caused a change? Also, what about the time
of the change? If not possible, do you think its useful to have this
available as part of couch core? Is it worth doing this via a plugin?
--
An Onion is the Onion skin and the Onion under the skin until the Onion
Skin without any Onion underneath.
--
_____________________________________________________________
The information contained in this communication is intended solely for the
use of the individual or entity to whom it is addressed and others
authorized to receive it. It may contain confidential or legally privileged
information. If you are not the intended recipient you are hereby notified
that any disclosure, copying, distribution or taking any action in reliance
on the contents of this information is strictly prohibited and may be
unlawful. If you have received this communication in error, please notify
us immediately by responding to this email and then delete it from your
system. The firm is neither liable for the proper and complete transmission
of the information contained in this communication nor for any delay in its
receipt.
Re: Changes API with user details
Posted by Dave Cottlehuber <dc...@jsonified.com>.
On 13 February 2014 14:09, Suraj Kumar <su...@inmobi.com> wrote:
> Hi,
>
> Is it possible to get which user caused a change? Also, what about the time
> of the change? If not possible, do you think its useful to have this
> available as part of couch core? Is it worth doing this via a plugin?
Hey Suraj,
These questions usually answer themselves when you put some key pieces
of info together"
1. replication is asynchronous and may take place over days, weeks or longer.
2. the "time" at which a change arrives at another instance may not
represent the time it arrived at the first instance.
3. you can put any info you like into a document, and use a validation
function to enforce it.
If that's not enough, please add some more info on your use case.
A+
Dave