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: Petr Jelinek <petr.jelinek@2ndquadrant.com>, 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-10T16:47:59Z
Lists: pgsql-hackers 
On 10.03.2017 05:07, Petr Jelinek wrote:
> The original complain was about JSON_VALUE extracting date but I don't
> understand why there is problem with that, the SQL/JSON defines that
> behavior. The RETURNING clause there is more or less just shorthand for
> casting with some advanced options.

Thanks for clarifying. I mistook it as if JSON_VALUE itself returns a 
date value.

Sven

Commits

  1. SQL/JSON: support the IS JSON predicate

  2. SQL/JSON: add standard JSON constructor functions