Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of simon@cloudant.com designates
 209.85.216.173 as permitted sender)
Date: Wed, 8 Jan 2014 09:33:57 -0500
From: Simon Metson <simon@cloudant.com>
To: user@couchdb.apache.org
Message-ID: <72C13018366C4AF7A23C3C5157AE791A@cloudant.com>
In-Reply-To: 
 <CAMAefes2KJoR_nKZxoFae+cUEyZA1sW=u+vk7ooGokviT=iw9g@mail.gmail.com>
References: 
 <CAMAefes2KJoR_nKZxoFae+cUEyZA1sW=u+vk7ooGokviT=iw9g@mail.gmail.com>
Subject: Re: CouchDB: Timestamp inaccurate and seems to be cached
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

You map function is only run when the data changes and the view needs to =
be rebuilt, so you=E2=80=99re not recording the time when you access view=
 but the time when the document was processed by the view. =20

Can you explain what you=E2=80=99re trying to achieve=3F Is there a reaso=
n you can=E2=80=99t get the current time in the client application=3F  =20


On Wednesday, 8 January 2014 at 09:17, Hank Knight wrote:

> I use this Map =46unction to get the current Unix timestamp:
> =20
> function(doc) =7Bemit(Math.round(new Date().getTime()/1000), null );=7D=

> =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=21 Is this due to caching or something
> else=3F What is the best way for me to always get the current Unix
> timestamp=3F