Re: FW: "=" operator vs. "IS"

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Rich Hall <rhall(at)micropat(dot)com>
Cc: pgsql-sql(at)postgresql(dot)org
Subject: Re: FW: "=" operator vs. "IS"
Date: 2004-06-29 14:57:45
Message-ID: 29590.1088521065@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

Rich Hall <rhall(at)micropat(dot)com> writes:
> My question is why is the form
> "(anything) = NULL"
> allowed?

If you think it shouldn't be, you can turn on the transform_null_equals
flag. However, past experience has shown that that breaks more things
than it fixes. In any case, few people like to depend on such a
thoroughly nonstandard behavior ...

regards, tom lane

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message Alexander M. Pravking 2004-06-29 16:17:42 UPDATE ... WHERE (subselect on the same table)
Previous Message Michael Kleiser 2004-06-29 14:47:01 Re: FW: "=" operator vs. "IS"