Re: SQL/JSON in PostgreSQL

From: "Sven R(dot) Kunze" <srkunze(at)mail(dot)de>
To: Peter van Hardenberg <pvh(at)pvh(dot)ca>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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-09 19:04:45
Message-ID: 1582d060-4d48-7097-021f-5c44607ddcaa@mail.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 09.03.2017 19:50, Peter van Hardenberg wrote:
> Anecdotally, we just stored dates as strings and used a convention
> (key ends in "_at", I believe) to interpret them. The lack of support
> for dates in JSON is well-known, universally decried... and not a
> problem the PostgreSQL community can fix.

I completely agree here.

Regards,
Sven

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2017-03-09 19:10:54 Re: Other formats in pset like markdown, rst, mediawiki
Previous Message Robert Haas 2017-03-09 19:01:42 Re: [PATCH] Add pg_disable_checksums() and supporting infrastructure