From: Tom Lane <tgl@sss.pgh.pa.us>
To: Rich Hall <rhall@micropat.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: FW: "=" operator vs. "IS"
Date: Tue, 29 Jun 2004 10:57:45 -0400
Message-ID: <29590.1088521065@sss.pgh.pa.us> (raw)
In-Reply-To: <40E17C81.3090308@micropat.com>
References: <7A4ADADFC8AFF0478D47F63BEDD57CE33A320C@gpmail.gphq.genpathpharma.com>
<40E17C81.3090308@micropat.com>
Rich Hall <rhall@micropat.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, rhall@micropat.com
Subject: Re: FW: "=" operator vs. "IS"
In-Reply-To: <29590.1088521065@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox