From: | Marcos Pegoraro <marcos(at)f10(dot)com(dot)br> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, Yugo NAGATA <nagata(at)sraoss(dot)co(dot)jp>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(at)eisentraut(dot)org>, David Rowley <dgrowleyml(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Document NULL |
Date: | 2024-11-21 15:02:51 |
Message-ID: | CAB-JLwZcw95W8-dvGaph3OX8VPLEwciYrE1kyAgvrrAhp2wVig@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em qui., 21 de nov. de 2024 às 11:42, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:
>
> I'm not following your train of thought here. Since null == null in
> json-land there isn't a need for or concept of "is distinct from". We tend
> to not expend space on pointing out things that don't exist.
>
But you said previously in this document about IS DISTINCT, so it's related
to NULL. I thought it would be better to mention that here, for JSON PATH,
that way doesn't exist.
"JSON null value is considered equal to other JSON null values, so here we
don't have the IS DISTINCT operator"
regards
Marcos
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2024-11-21 15:03:52 | Re: Document NULL |
Previous Message | yuansong | 2024-11-21 15:02:46 | backup server core when redo btree_xlog_insert that type is XLOG_BTREE_INSERT_POST |