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 jeanfelixg@icloud.com
 designates 17.172.108.249 as permitted sender)
From: Jean-Felix Girard <jeanfelixg@icloud.com>
Content-type: multipart/alternative;
 boundary="Apple-Mail=_3B07E136-3765-489F-8556-5FFD1602B5AD"
Message-id: <7231BBE3-83BD-4C83-9B61-A49CB1335957@icloud.com>
MIME-version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: CouchDB: Timestamp inaccurate and seems to be cached
Date: Wed, 08 Jan 2014 14:40:09 -0500
References: 
 <CAMAefes2KJoR_nKZxoFae+cUEyZA1sW=u+vk7ooGokviT=iw9g@mail.gmail.com>
 <CAMAefeuyxsmdit7kyOTJQq3qp0Mrh--1Z7uMv-cg4emeG9Zi0Q@mail.gmail.com>
To: user@couchdb.apache.org
In-reply-to: 
 <CAMAefeuyxsmdit7kyOTJQq3qp0Mrh--1Z7uMv-cg4emeG9Zi0Q@mail.gmail.com>

--Apple-Mail=_3B07E136-3765-489F-8556-5FFD1602B5AD
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=iso-8859-1

I just noticed that Couchdb returns a "Date" response header.

< HTTP/1.1 200 OK
< Transfer-Encoding: chunked
< Server: CouchDB/1.5.0 (Erlang OTP/R16B02)
< ETag: "4E9MYK7J4X9CKM0EUK0V1K7IZ"
< Date: Wed, 08 Jan 2014 19:34:38 GMT
< Content-Type: text/plain; charset=3Dutf-8
< Cache-Control: must-revalidate

You can parse that date (from the GET request on the view) and compare =
it to the document date to find out theirs age.

Jeff


On Jan 8, 2014, at 1:58 PM, Hank Knight <hknight555@gmail.com> wrote:

> I want to get the current timestamp according to the CouchDB server
> using a GET request.  When new documents are created, an update
> function is used to add a timestamp to a document.  When I get a
> result set, it is important to know the server's current timestamp so
> the age of the documents in the result set can be correctly
> determined.
>=20
> On Wed, Jan 8, 2014 at 10:17 AM, Hank Knight <hknight555@gmail.com> =
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?


--Apple-Mail=_3B07E136-3765-489F-8556-5FFD1602B5AD--