Horton

Re: SQL/JSON in PostgreSQL

Nico Williams <nico@cryptonector.com>

View thread View on postgr.es
From: Nico Williams <nico@cryptonector.com>
To: "Sven R. Kunze" <srkunze@mail.de>
Cc: Magnus Hagander <magnus@hagander.net>, Peter van Hardenberg <pvh@pvh.ca>, 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-13T06:24:39Z
Lists: pgsql-hackers 
On Thu, Mar 09, 2017 at 07:12:07PM +0100, Sven R. Kunze wrote:
> From my day-to-day work I can tell, the date(time) type is the only missing
> piece of JSON to make it perfect for business applications (besides, maybe,
> a "currency" type).

And a binary type.  And a chunked-string type (to avoid having to escape
strings).  And an interval type.  And...

Commits

  1. SQL/JSON: support the IS JSON predicate

  2. SQL/JSON: add standard JSON constructor functions