Message-ID: <9314cf1402ee27d287b24d3a7622f7dc78d6ea34.camel@cybertec.at>
Subject: Re: Postgres jsonb data
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: stephen@infowerks.com, pgsql-docs@lists.postgresql.org
Date: Wed, 21 May 2025 08:12:06 +0200
In-Reply-To: 
 <174774849023.1455382.3103677107495562713@wrigleys.postgresql.org>
References: 
	<174774849023.1455382.3103677107495562713@wrigleys.postgresql.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.56.1 (3.56.1-1.fc42) 
MIME-Version: 1.0
Archived-At: 
 <https://www.postgresql.org/message-id/9314cf1402ee27d287b24d3a7622f7dc78d6ea34.camel%40cybertec.at>
Precedence: bulk

On Tue, 2025-05-20 at 13:41 +0000, PG Doc comments form wrote:
> Page: https://www.postgresql.org/docs/14/datatype-json.html
>=20
> Documentation suggests that a json type of null doesn't turn into anythin=
g
> when read into a jsonb, because the json type of null doesn't correspond =
to
> the postgres type of NULL.  We've found that in fact it's treated the sam=
e
> as the string "null" - and the documentation probably should reflect this
> edge case.

I see them treated differently:

SELECT 'null'::jsonb IS NULL;
 ?column?=20
=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=95=90=E2=
=95=90=E2=95=90
 f
(1 row)

Can you show examples of what you mean?

Yours,
Laurenz Albe