| From: | Vik Fearing <vik(at)postgresfriends(dot)org> |
|---|---|
| To: | Erki Eessaar <erki(dot)eessaar(at)taltech(dot)ee>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: JSON type unsupported |
| Date: | 2023-09-26 15:31:11 |
| Message-ID: | d180d17c-c48c-762e-f647-48da195f3272@postgresfriends.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On 9/26/23 11:33, Erki Eessaar wrote:
> Hello
>
> According to Appendix D. SQL Conformance
>
> https://www.postgresql.org/docs/current/unsupported-features-sql-standard.html
>
> the feature T801 JSON data type is unsupported. However, PostgreSQL has data types JSON and JSONB. Here (http://peter.eisentraut.org/blog/2023/04/18/postgresql-and-sql-2023) it is also said that T801 is supported.
>
> Perhaps there are some technical details that I am not aware of. However, I wanted to point this out.
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.
[1] This is a fully specified parsing function, not just a cast like we
have today.
--
Vik Fearing
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-09-26 15:44:42 | Re: correct documentation in set role |
| Previous Message | Erki Eessaar | 2023-09-26 09:33:46 | JSON type unsupported |