From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | divergentdave(at)gmail(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: "jsonb ? text" operator and JSON strings |
Date: | 2022-11-28 21:29:56 |
Message-ID: | CAKFQuwYhCoUupuGgVM4DQ_ZNc4g2gVdHsdV2ct7EeQCEaUdQ1w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
On Mon, Nov 28, 2022 at 1:34 PM PG Doc comments form <noreply(at)postgresql(dot)org>
wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/14/functions-json.html
> Description:
>
> The description of the "jsonb ? text" operator in table 9.45 specifies its
> behavior when the jsonb value is an object or an array, but not when it is
> a
> string, number, or the null JSON object. One of the examples in 8.14.3
> says,
> in a comment, "A string is considered to exist if it matches a primitive
> JSON string". I think the behavior of the operator on each JSON primitive
> type should be spelled out in prose somewhere.
>
I suppose we shouldn't imply it doesn't work on non-containers since it
obviously does. And by fixing that omission state clearly that on a
non-container existence and containment are equivalent and based upon
equality.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Matous Jan Fialka | 2022-11-29 08:40:47 | Tutorial book with runable code for Postgres? |
Previous Message | David G. Johnston | 2022-11-28 19:50:07 | Re: nextval parameter is not clear |