Mailing-List: contact user-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@couchdb.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 juanjo@comellas.org does not designate 209.85.161.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CABvT1DGGYCuw=gLT1d6FO-GtWahh1CTiVWWD-7YATQb1rfwqYA@mail.gmail.com>
References: 
 <CAFov+BLFu-b16iTwrrOr4C_6z1r50ajN5zSVNRE9FODe3ihtHQ@mail.gmail.com>
	<CAOLqyqy-wRmmjW3_UibWMj-iOW15dKohq3Jv1S4uakfQQUskxg@mail.gmail.com>
	<CABvT1DGGYCuw=gLT1d6FO-GtWahh1CTiVWWD-7YATQb1rfwqYA@mail.gmail.com>
Date: Wed, 6 Jul 2011 12:14:24 -0300
Message-ID: 
 <CAOLqyqw0pCxL5Z91HpDF9uV=C7n_bnSuh3mJ8Aw0go07-JbxRw@mail.gmail.com>
Subject: Re: json date representations
From: Juan Jose Comellas <juanjo@comellas.org>
To: user@couchdb.apache.org
Content-Type: multipart/alternative; boundary=00151747858241565704a7680e67

--00151747858241565704a7680e67
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I know, but the ISO 8601 format is much bulkier, and when you store hundred=
s
of millions of records with a minimum of two timestamps per document, it
quickly adds up. Besides, it makes it much easier to make timestamp
calculations in the views.

Juanjo


On Wed, Jul 6, 2011 at 12:02 PM, Robert Newson <rnewson@apache.org> wrote:

> ISO 8601 allows nanosecond precision;
>
> "Decimal fractions may also be added to any of the three time
> elements... A fraction may only be added to the lowest order time
> element in the representation... There is no limit on the number of
> decimal places for the decimal fraction"
>
> B.
>
> On 6 July 2011 15:53, Juan Jose Comellas <juanjo@comellas.org> wrote:
> > We use CouchDB for a telephony application where we sometimes need
> subsecond
> > precision, so we store timestamps as floating point numbers, where the
> > integer part corresponds to the seconds and the decimal part to the
> > {milli,micro,nano}seconds since the Unix epoch (Jan 1, 1970). The nice
> thing
> > about this format is that it can be used both for absolute (a date) and
> > relative (the offset at which an event occurred) timestamps and you can
> > easily perform arithmetic operations between them.
> >
> >
> > 2011/7/5 Rudi Benkovi=C4=8D <rudib@whiletrue.com>
> >
> >> Hi,
> >>
> >> I'm writing a little CouchDB administration utility and would like to
> >> find out how most of you store data values in JSON. From .NET via
> >> Newtonsoft's JSON serializer, dates end up in the ISO 8601 as a
> >> string, like this:
> >>
> >> { Timestamp": "2011-05-12T20:52:02.3774261Z" }
> >>
> >> Let me know what other formats are used, as I'd like to cover as much
> >> of them as possible - hopefully the Javascript view code will be able
> >> to detect them automatically.
> >>
> >> Thanks!
> >>
> >> Rudi
> >>
> >
>

--00151747858241565704a7680e67--