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 dmitriy.fot@gmail.com
 designates 209.85.220.180 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <857D6498-4A9B-4D8B-BDA2-CFEAA6DD7B2B@couchbase.com>
References: 
 <CANJeXJTBGRTHsXVzXVP7jpbnZ_GwHbQRE6VFJ3am+yQaHnyQ=g@mail.gmail.com>
 <857D6498-4A9B-4D8B-BDA2-CFEAA6DD7B2B@couchbase.com>
From: Dmitriy Fot <dmitriy.fot@gmail.com>
Date: Sun, 9 Dec 2012 20:04:57 +0100
Message-ID: 
 <CANJeXJR7HBsuavtfs6SavWG1yp_-cgabgiqaYx+dQdoB8U9xPg@mail.gmail.com>
Subject: Re: CouchDB document design for facebook insights
To: user@couchdb.apache.org
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

great responses, thank you guys,

Dmitriy Fot
---------------------------------
dmitriy.fot@gmail.com


On 7 December 2012 19:51, Jens Alfke <jens@couchbase.com> wrote:
>
> On Dec 7, 2012, at 12:32 AM, Dmitriy Fot <dmitriy.fot@gmail.com<mailto:dm=
itriy.fot@gmail.com>> wrote:
>
> - Is it right decision to use an array for the timestamp, or it is
> better to use a long?
>
> Depends what you=92ll be using it for. The array you have is great if you=
=92ll be doing a lot of tests based on the components of the date, i.e. all=
 the posts from November 2012. If you just need to compare times or look at=
 the interval between two times, a numeric timestamp is best (at the expens=
e of not being directly human-readable.) A string timestamp is more compact=
 than an array and can be converted into either a number or components by t=
he JS Date class, although the conversion is somewhat expensive.
>
> (Another thing to consider about timestamps is whether you need to rememb=
er the time zone or not. For most purposes you can just pre-convert everyth=
ing to UTC, but for some queries you might want to know the local time, i.e=
. =93what time of day do people post most often?=94)
>
> =97Jens