| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Navrátil, Ondřej <onavratil(at)monetplus(dot)cz> |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: COALESCE documentation |
| Date: | 2024-07-03 14:41:19 |
| Message-ID: | d67def4741aec22bb16a10fb7dcbae4086daf125.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wed, 2024-07-03 at 11:42 +0200, Navrátil, Ondřej wrote:
> On a side note, I tested similar behavior in Oracle databases, and for them, something like
> select testtype(null, null) is null; -- returns 0 (false)
> select testtype(null, null) is not null; -- returns 1 (true)
> ...and as far as I could test, in Oracle the IS NULL and IS NOT NULL operators are truly dual
That only goes to say that Oracle is not very standard compliant, but
I wouldn't expect anything else from a system where '' IS NULL.
Yours,
Laurenz Albe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2024-07-03 14:57:48 | Re: COALESCE documentation |
| Previous Message | David G. Johnston | 2024-07-03 12:34:57 | Re: COALESCE documentation |