From: Tom Lane <tgl@sss.pgh.pa.us>
To: Vik Fearing <vik@postgresfriends.org>
cc: Erki Eessaar <erki.eessaar@taltech.ee>,
        "pgsql-docs@lists.postgresql.org" <pgsql-docs@lists.postgresql.org>,
        Peter Eisentraut <peter@eisentraut.org>
Subject: Re: JSON type unsupported
In-reply-to: <d180d17c-c48c-762e-f647-48da195f3272@postgresfriends.org>
References: 
 <AS8PR01MB82592A6675A14CE5E5FFFE5AFEC3A@AS8PR01MB8259.eurprd01.prod.exchangelabs.com>
 <d180d17c-c48c-762e-f647-48da195f3272@postgresfriends.org>
Comments: In-reply-to Vik Fearing <vik@postgresfriends.org>
	message dated "Tue, 26 Sep 2023 17:31:11 +0200"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <429311.1695749097.1@sss.pgh.pa.us>
Date: Tue, 26 Sep 2023 13:24:57 -0400
Message-ID: <429312.1695749097@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/429312.1695749097%40sss.pgh.pa.us>
Precedence: bulk

Vik Fearing <vik@postgresfriends.org> writes:
> Thank you for pointing this out.  Peter's blog is slightly misleading in 
> that we do have the JSON data type, but the T801 feature is far from 
> complete.

> For example, we do not have the JSON_SERIALIZE(), JSON()[1], 
> JSON_SCALAR() functions.  We don't have the IS JSON predicate, or a few 
> other things hiding behind T801.

> All in all, I would not say we support the JSON data type the way the 
> standard intends, and therefore we should not claim to support T801.

Agreed, but should we say "partial support", as we do for some other
feature identifiers?

			regards, tom lane