Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL - Mailing list pgsql-bugs

From Andrew Gierth
Subject Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL
Date
Msg-id 87mvl9qkog.fsf@news-spur.riddles.org.uk
Whole thread Raw
In response to Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL
List pgsql-bugs
>>>>> "Tom" == Tom Lane <tgl@sss.pgh.pa.us> writes:

 Tom> But that still leaves us with ten years of history in which we
 Tom> *were* conforming to the spec, modulo the very narrow corner case
 Tom> mentioned in this thread.

Yeah, but the main visible effect of that has been a stream of "you have
to use NOT (x IS NULL) rather than (x IS NOT NULL)" responses to people
having trouble with this.

Is there a single reported case where anyone has actually needed the
spec's version of (x IS NOT NULL) for a composite type?

--
Andrew (irc:RhodiumToad)

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL
Next
From: Tom Lane
Date:
Subject: Re: BUG #14235: inconsistencies with IS NULL / IS NOT NULL