Postgres Pro
Downloads
Home   >   mailing lists

"=" operator vs. "IS" - Mailing list pgsql-sql

From Stefan Weiss
Subject "=" operator vs. "IS"
Date
Msg-id 200406290002.29099.spaceman@foo.at
Whole thread Raw
Responses Re: "=" operator vs. "IS"  (Steve Crawford <scrawford@pinpointresearch.com>)
Re: "=" operator vs. "IS"  (Michael A Nachbaur <mike@nachbaur.com>)
List pgsql-sql
Tree view 
Hi.

I'm just curious - why is it not possible to use the "=" operator to
compare values with NULL? I suspect that the SQL standard specified
it that way, but I can't see any ambiguity in an expression like "AND
foo.bar = NULL". Is it because NULL does not "equal" any value, and the
expression should be read as "foo.bar is unknown"? Or is there something
else I'm missing?

If it's the "unknown" part, then why can't I use "=" to compare with
TRUE or FALSE?


cheers,
stefan

pgsql-sql by date:

Previous
From: Greg Stark
Date:
Subject: Re: Empty array IS NULL?
Next
From: "Dmitri Bichko"
Date:
Subject: FW: "=" operator vs. "IS"