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: local policy includes SPF record at
 spf.trusted-forwarder.org)
Content-Type: text/plain; charset=iso-8859-1
Mime-Version: 1.0 (Apple Message framework v1283)
Subject: Re: CouchDB: Timestamp inaccurate and seems to be cached
From: Filippo Fadda <filippo.fadda@programmazione.it>
In-Reply-To: 
 <CAMAefes2KJoR_nKZxoFae+cUEyZA1sW=u+vk7ooGokviT=iw9g@mail.gmail.com>
Date: Wed, 8 Jan 2014 15:44:37 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <C3052A85-194F-4974-BF8A-0AFED332336C@programmazione.it>
References: 
 <CAMAefes2KJoR_nKZxoFae+cUEyZA1sW=u+vk7ooGokviT=iw9g@mail.gmail.com>
To: user@couchdb.apache.org

I suggest to generate the timestamp when you save the document, not when =
you index it.

-Filippo

On Jan 8, 2014, at 3:17 PM, Hank Knight wrote:

> I use this Map Function to get the current Unix timestamp:
>=20
> function(doc) {emit(Math.round(new Date().getTime()/1000), null  );}
>=20
> The odd thing is, it returns a correct timestamp the first time I run
> a query but it returns the exact same timestamp one minute later even
> though 60 seconds have passed!  Is this due to caching or something
> else?  What is the best way for me to always get the current Unix
> timestamp?