| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: strange IS NULL behaviour |
| Date: | 2013-09-05 01:26:28 |
| Message-ID: | 20130905012628.GV21874@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 3, 2013 at 09:32:44PM -0400, Bruce Momjian wrote:
> In this test, SELECT NULL (which internally would produce SELECT
> ROW(NULL)), returns TRUE, while SELECT ROW(NULL) and further nesting
> returns false.
>
> This has made me adjust my goal and change it so SELECT ROW(NULL) IS
> NULL returns true, and any further nesting returns false.
>
> Attached is a patch which accomplishes this, and a documentation update.
I have not heard any feedback on this patch, so I would like to apply it
to give us a nested ROW/IS NULL API we can document. It would have to
be marked in the release notes as a backward incompatibility.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ It's impossible for everything to be true. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Quan Zongliang | 2013-09-05 03:02:47 | Re: improve Chinese locale performance |
| Previous Message | Noah Misch | 2013-09-05 01:17:47 | Re: Frontend/backend protocol improvements proposal (request). |