From: Greg Stark <gsstark@mit.edu>
To: Rich Hall <rhall@micropat.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: FW: "=" operator vs. "IS"
Date: 29 Jun 2004 13:37:21 -0400
Message-ID: <87wu1qxo32.fsf@stark.xeocode.com> (raw)
In-Reply-To: <40E17C81.3090308@micropat.com>
References: <7A4ADADFC8AFF0478D47F63BEDD57CE33A320C@gpmail.gphq.genpathpharma.com>
<40E17C81.3090308@micropat.com>
Rich Hall <rhall@micropat.com> writes:
> "(anything) = NULL" is always Null, this cannot be what the coder intended.
I often have such things in my SQL. Consider what happens when you have SQL
constructed dynamically. Or more frequently, consider that many drivers still
don't use the new binary placeholder syntax and emulate it by putting the
parameters directly into the SQL.
--
greg
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: gsstark@mit.edu, rhall@micropat.com
Subject: Re: FW: "=" operator vs. "IS"
In-Reply-To: <87wu1qxo32.fsf@stark.xeocode.com>
* 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