Re: Proposal: revert behavior of IS NULL on row types

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:04:30
Message-ID: 87r3alql9s.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:

>> 2. x IS NOT NULL if and only if NOT (x IS NULL)

David> ​I would rather prohibit "IS NOT NULL" altogether.​ If one needs
David> to test "NOT (x IS NULL)" they can write it that way.

Prohibiting IS NOT NULL is not on the cards; it's very widely used.

>> Whole-row vars when constructed never contain the null value.

David> ...but what does this mean in end-user terms?​

It means for example that this query:

select y from x left join y on (x.id=y.id) where y is null;

would always return 0 rows.

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Gierth 2016-07-23 00:21:19 Re: Proposal: revert behavior of IS NULL on row types
Previous Message David G. Johnston 2016-07-22 23:54:24 Re: Proposal: revert behavior of IS NULL on row types