| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(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-07-05 15:03:56 |
| Message-ID: | 19613.1373036636@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Jul 4, 2013 at 04:29:20PM -0400, Tom Lane wrote:
>> No, it isn't, or at least it's far from the only place. If we're going
>> to change this, we would also want to change the behavior of tests on
>> RECORD values, which is something that would have to happen at runtime.
> I checked RECORD and that behaves with recursion:
Apparently you don't even understand the problem. All of these examples
you're showing are constants. Try something like
declare r record;
...
select ... into r ...
if (r is null) ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2013-07-05 15:05:46 | Re: Review: UNNEST (and other functions) WITH ORDINALITY |
| Previous Message | Vik Fearing | 2013-07-05 14:58:30 | Re: Review: UNNEST (and other functions) WITH ORDINALITY |