Re: [HACKERS] SQL/JSON in PostgreSQL - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] SQL/JSON in PostgreSQL
Date
Msg-id 47ddb016-a6e7-0ca1-a035-cdc64c31bdfd@2ndquadrant.com
Whole thread Raw
In response to Re: [HACKERS] SQL/JSON in PostgreSQL  (Peter van Hardenberg <pvh@pvh.ca>)
Responses Re: [HACKERS] SQL/JSON in PostgreSQL  ("Sven R. Kunze" <srkunze@mail.de>)
Re: [HACKERS] SQL/JSON in PostgreSQL  (Oleg Bartunov <obartunov@gmail.com>)
List pgsql-hackers
On 09/03/17 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.
> 

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.

--  Petr Jelinek                  http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: [HACKERS] foreign partition DDL regression tests
Next
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] [PATCH] Use $ parameters as replacement characters forpg_stat_statements