From: | Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Proposal: revert behavior of IS NULL on row types |
Date: | 2016-07-23 00:21:19 |
Message-ID: | 87invxqkfz.fsf@news-spur.riddles.org.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>>>>> "David" == David G Johnston <david(dot)g(dot)johnston(at)gmail(dot)com> writes:
>> 1. x IS NULL is true if and only if x has the null value (isnull set).
David> I don't have a problem conforming to "ROW(NULL, NULL) IS NULL"
David> being true...if you somehow get a hold of something in that
David> form, which your others points address.
This seems harmless, but I think it's not worth the pain.
I'm informed that for example on Oracle:
select case when foo_type(null, null) is null
then 'true' else 'false'
end from dual;
returns 'false'.
--
Andrew (irc:RhodiumToad)
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2016-07-23 00:25:10 | Re: Proposal: revert behavior of IS NULL on row types |
Previous Message | Andrew Gierth | 2016-07-23 00:04:30 | Re: Proposal: revert behavior of IS NULL on row types |