Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (nike.apache.org: domain of dch@jsonified.com designates
 209.85.217.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABadZm+kiy=QCDFj-=i0KMz6BMiPvezAE_vVr0QNB1-e_o7OLQ@mail.gmail.com>
References: 
 <CABadZm+kiy=QCDFj-=i0KMz6BMiPvezAE_vVr0QNB1-e_o7OLQ@mail.gmail.com>
Date: Thu, 13 Feb 2014 15:08:20 +0100
Message-ID: 
 <CAL+Y1nvFGUm1HBY3BuWDjZ0vgysWsu=NWOcgbn8pOxDg27qKAQ@mail.gmail.com>
Subject: Re: Changes API with user details
From: Dave Cottlehuber <dch@jsonified.com>
To: user@couchdb.apache.org
Content-Type: text/plain; charset=UTF-8

On 13 February 2014 14:09, Suraj Kumar <suraj.kumar@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