| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Erik Wienhold <ewie(at)ewie(dot)name> |
| Cc: | Bob Kline <bkline(at)rksystems(dot)com>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Inclusion of json in list of standard data types |
| Date: | 2025-12-08 19:36:43 |
| Message-ID: | 3100801.1765222603@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Erik Wienhold <ewie(at)ewie(dot)name> writes:
> But does Postgres' json type really map to the JSON type defined by
> SQL:2023? jsonb appears to be closer to that, although I don't have
> access to that particular version of the standard. Peter wrote [1]
> about the compatibility with SQL:2023 and noted that the standard maps
> more readily to jsonb (see 3rd bullet point in the notes section) and
> features T879–T882 still only apply to jsonb.
Well, there is the weasel wording right at the start of that <note>:
The following types (or spellings thereof) are specified by SQL:
This note also doesn't get into the rather large semantic gap between
what SQL says TIMESTAMP WITH TIME ZONE is and what timestamptz
actually does. I think the point of the note is mostly to say that
"you have some hope of interoperability with other DBMSes if you
use these types".
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | grant@scarydba.com | 2025-12-12 15:47:33 | Volunteering |
| Previous Message | Erik Wienhold | 2025-12-08 18:39:52 | Re: Virtual Generated Columns |