| From: | Nico Williams <nico(at)cryptonector(dot)com> |
|---|---|
| To: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Oleg Bartunov <obartunov(at)gmail(dot)com>, David Steele <david(at)pgmasters(dot)net>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org>, Nikita Glukhov <n(dot)gluhov(at)postgrespro(dot)ru>, Teodor Sigaev <teodor(at)postgrespro(dot)ru>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, andrew Dunstan <andrew(at)dunslane(dot)net> |
| Subject: | Re: SQL/JSON in PostgreSQL |
| Date: | 2017-03-13 06:14:03 |
| Message-ID: | 20170313061402.GA543@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 07, 2017 at 10:43:16PM +0100, Sven R. Kunze wrote:
> about the datetime issue: as far as I know, JSON does not define a
> serialization format for dates and timestamps.
Use strings in ISO 8601 format, with or without fractional seconds, and
maybe with 5-digit years.
> On the other hand, YAML (as a superset of JSON) already supports a
> language-independent date(time) serialization format
> (http://yaml.org/type/timestamp.html)
But YAML isn't what this is about.
Nico
--
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2017-03-13 06:15:06 | Re: possible encoding issues with libxml2 functions |
| Previous Message | Beena Emerson | 2017-03-13 06:06:53 | Re: increasing the default WAL segment size |