Skip site navigation (1) Skip section navigation (2)

Re: BUG #6064: != NULL, <> NULL do not work [sec=UNCLASSIFIED]

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: "Pilling, Michael" <Michael(dot)Pilling(at)dsto(dot)defence(dot)gov(dot)au>
Cc: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6064: != NULL, <> NULL do not work [sec=UNCLASSIFIED]
Date: 2011-06-20 00:39:55
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On 20/06/2011 8:30 AM, Pilling, Michael wrote:

> I was looking at that page but didn't read the detail because I thought
> the information was in the table and the detail was just textual examples.

I do think that adding "IS DISTINCT FROM" and "IS NULL / IS NOT NULL" to 
the summary table would be helpful, with a superscript * linking to  the 
note about null handling below.

In general, though, there's only so much information that can be 
condensed into the brief summary and tables.

Reading the documentation in detail is a really, really good idea. It'll 
tell you a lot about Pg and about SQL in general. I've generally found 
it really helpful and not at all long-winded. It's pretty much how I 
learned to use relational databases.

In this case the documentation even has a big box-out saying:

"Tip: Some applications might expect that expression = NULL returns true 
if expression evaluates to the null value."

... that carries on to explain about NULLs.

Craig Ringer

Tech-related writing at

In response to

pgsql-bugs by date

Next:From: Jeff DavisDate: 2011-06-20 06:19:33
Subject: Re: BUG #6064: != NULL, <> NULL do not work [sec=UNCLASSIFIED]
Previous:From: Craig RingerDate: 2011-06-20 00:35:10
Subject: Re: BUG #6064: != NULL, <> NULL do not work [sec=UNCLASSIFIED]

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group