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 mrtrick@gmail.com designates
 209.85.161.180 as permitted sender)
Message-ID: <4E13A6B2.2040708@gmail.com>
Date: Wed, 06 Jul 2011 10:05:06 +1000
From: Patrick Barnes <mrtrick@gmail.com>
User-Agent: Mozilla/5.0 (Windows NT 5.1;
 rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: user@couchdb.apache.org
Subject: Re: json date representations
References: 
 <CAFov+BLFu-b16iTwrrOr4C_6z1r50ajN5zSVNRE9FODe3ihtHQ@mail.gmail.com>
In-Reply-To: 
 <CAFov+BLFu-b16iTwrrOr4C_6z1r50ajN5zSVNRE9FODe3ihtHQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

I use ISO8601 as well; "2010-08-29T13:07:49+10:00"
(generated using PHP date('c');)

On 6/07/2011 9:49 AM, Rudi Benkovič wrote:
> 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
>