Horton

Re: SQL/JSON in PostgreSQL

Sven R. Kunze <srkunze@mail.de>

View thread View on postgr.es
From: "Sven R. Kunze" <srkunze@mail.de>
To: Peter van Hardenberg <pvh@pvh.ca>
Cc: Robert Haas <robertmhaas@gmail.com>, Andres Freund <andres@anarazel.de>, Oleg Bartunov <obartunov@gmail.com>, David Steele <david@pgmasters.net>, Pavel Stehule <pavel.stehule@gmail.com>, Pgsql Hackers <pgsql-hackers@postgresql.org>, Nikita Glukhov <n.gluhov@postgrespro.ru>, Teodor Sigaev <teodor@postgrespro.ru>, Alexander Korotkov <a.korotkov@postgrespro.ru>, andrew Dunstan <andrew@dunslane.net>
Date: 2017-03-09T19:04:45Z
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

Commits

  1. SQL/JSON: support the IS JSON predicate

  2. SQL/JSON: add standard JSON constructor functions