Re: SQL/JSON in PostgreSQL

From: Nico Williams <nico(at)cryptonector(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "Sven R(dot) Kunze" <srkunze(at)mail(dot)de>, Peter van Hardenberg <pvh(at)pvh(dot)ca>, 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-13 06:16:51
Message-ID: 20170313061650.GB543@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Mar 09, 2017 at 12:58:55PM -0500, Robert Haas wrote:
> On Thu, Mar 9, 2017 at 12:48 PM, Sven R. Kunze <srkunze(at)mail(dot)de> wrote:
> > 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
>
> But there's apparent sophistry, like this, in that spec:

I agree with you. But beware, the IETF has had multiple threads with
thousands of posts in them about these sorts of issues. If you're not
careful you'll have such a thread on this list too. It would be very
sad not to only let a group that really cares have such threads instead.

:)

Nico
--

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Victor Yegorov 2017-03-13 06:22:22 Re: Relation cache invalidation on replica
Previous Message Pavel Stehule 2017-03-13 06:15:06 Re: possible encoding issues with libxml2 functions