| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Vik Fearing <vik(at)postgresfriends(dot)org> |
| Cc: | 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>, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: JSON type unsupported |
| Date: | 2023-09-26 17:24:57 |
| Message-ID: | 429312.1695749097@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Vik Fearing <vik(at)postgresfriends(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2023-09-26 17:34:56 | Re: pg_upgrade doc uses inconsistent versions within the doc. |
| Previous Message | Bruce Momjian | 2023-09-26 15:44:42 | Re: correct documentation in set role |