From: | "Sven R(dot) Kunze" <srkunze(at)mail(dot)de> |
---|---|
To: | Peter van Hardenberg <pvh(at)pvh(dot)ca> |
Cc: | 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 17:48:52 |
Message-ID: | 3115c420-48ac-78c8-d543-d05dc63da85b@mail.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 08.03.2017 20:48, Peter van Hardenberg wrote:
> Small point of order: YAML is not strictly a super-set of JSON.
I haven't read the whole standard, but from what I can see the standard
considers JSON an official subset of itself:
http://www.yaml.org/spec/1.2/spec.html
Regards,
Sven
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-03-09 17:54:03 | Re: use SQL standard error code for nextval |
Previous Message | Peter Eisentraut | 2017-03-09 17:48:05 | Re: Logical replication existing data copy |