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-12-09 18:30:29 |
Message-ID: | CAB-JLwZL=jA-i3X9Gw=s4YH5FgA8f-tKWkCUqtyRrrSDcjL_NA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Em seg., 9 de dez. de 2024 às 13:31, David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> escreveu:
> I'm OK with adding more cross-references (links or just brief comparative
> verbiage like the above) to non-SQL null value treatment but this document,
> for this patch, is going to focus solely on SQL NULL.
>
If you briefly mention JSON NULLs, it might be interesting to also
briefly mention that in other places NULL can be seen differently,
including changing its name. A SQL NULL passed as argument to a PL/Python
function will be named None or PL/Perl will be undefined.
regards,
Marcos
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2024-12-09 18:47:37 | Re: Parallel heap vacuum |
Previous Message | Andrey M. Borodin | 2024-12-09 18:26:02 | Re: [PATCH] Add sortsupport for range types and btree_gist |