From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Brian Mendoza <brian(at)rotamap(dot)net>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: JSONB operator unanticipated behaviour |
Date: | 2023-05-18 17:41:48 |
Message-ID: | 8e946df1-ae6a-c9c6-8e99-942923dae6f2@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 5/18/23 09:36, Tom Lane wrote:
> Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> writes:
>> On 5/18/23 08:46, Tom Lane wrote:
>>> You seem to be reading some fairly old version of the documentation.
>>> The extended definition that Adrian mentions has been there for
>>> awhile, but the JSON operator table didn't link to it before v13.
>>> (I agree that the "top level" bit was just wrong, but it's gone.)
>
>> Can you elaborate on gone and/or wrong as I see it in the 15 and devel
>> documentation.
>
> In v12 (and probably earlier, didn't look) Table 9.45 defines @> as
> "Does the left JSON value contain the right JSON path/value entries
> at the top level?" [1].
Alright I get it now.
>
> regards, tom lane
>
> [1] https://www.postgresql.org/docs/12/functions-json.html
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ron | 2023-05-18 17:49:20 | Re: Would PostgreSQL 16 native transparent data encryption support database level encryption? |
Previous Message | Arora, Nick | 2023-05-18 17:28:38 | Unrecognized Node Type Warning |