From: | Joe Van Dyk <joe(at)tanga(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: to_json(now()) result doesn't have 'T' separator |
Date: | 2013-12-21 00:24:16 |
Message-ID: | CACfv+pK2veWXy+y=DC_nQDBtsb-ohVTns3YT28L+J+29VF9yLQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, Dec 20, 2013 at 4:18 PM, Joe Van Dyk <joe(at)tanga(dot)com> wrote:
> # select to_json(now());
> to_json
> ---------------------------------
> "2013-12-20 15:53:39.098204-08"
> (1 row)
>
> I'd like to see it output "2013-12-20T15:53:39.098204-08" so it's
> interchangeable with more systems.
>
Actually, "2013-12-20T15:53:39.44553-08:00" would be ideal.
>
>
> http://en.wikipedia.org/wiki/ISO_8601#Combined_date_and_time_representationssays 'T' can be omitted "by mutual agreement".
>
> I'm working with javascript/json systems that expect the 'T' to be there
> however, so there's no mutual agreement happening.
>
> Thoughts? I know I can hack around it by specifying my own date format,
> but I'd really like to be able to use row_to_json and other functions
> without specifying custom date formats everywhere.
>
> Joe
>
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2013-12-21 00:37:11 | Re: pg_upgrade & tablespaces |
Previous Message | David Johnston | 2013-12-21 00:20:17 | Re: Seems like bug in 9.1.3, need to confirm. |