From: Tom Lane <tgl@sss.pgh.pa.us>
To: Stephan Szabo <sszabo@megazone23.bigpanda.com>
Cc: Mark Stosberg <mark@summersault.com>
Cc: pgsql-sql@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
Date: Wed, 06 Jun 2001 22:19:42 -0400
Message-ID: <6689.991880382@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.BSF.4.21.0106061809050.18346-100000@megazone23.bigpanda.com>
References: <Pine.BSF.4.21.0106061809050.18346-100000@megazone23.bigpanda.com>
Stephan Szabo <sszabo@megazone23.bigpanda.com> writes:
> Yes, column = NULL should *never* return true according to the spec (it
> should always return NULL in fact as stated). The reason for breaking
> with the spec is AFAIK to work with broken microsoft clients that seem to
> think that =NULL is a meaningful test and generate queries using that.
Microsoft Access is the guilty party, IIRC. I recently tried to stir up
some interest in changing this behavior back to the standard, but
apparently there are still too many people using broken versions of
Access.
A compromise answer might be to offer a SET variable that selects the
Microsoft-compatible misimplementation. Would that fly?
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, sszabo@megazone23.bigpanda.com, mark@summersault.com, pgsql-hackers@postgresql.org
Subject: Re: behavior of ' = NULL' vs. MySQL vs. Standards
In-Reply-To: <6689.991880382@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