From: Tom Lane <tgl@sss.pgh.pa.us>
To: Tod McQuillin <devin@spamcop.net>
Cc: Kovacs Baldvin <kb136@hszk.bme.hu>
Cc: pgsql-sql@postgresql.org
Subject: Re: Intentional, or bug?
Date: Sun, 16 Sep 2001 15:31:07 -0400
Message-ID: <18429.1000668667@sss.pgh.pa.us> (raw)
In-Reply-To: <20010916235732.G46039-100000@glass.pun-pun.prv>
References: <20010916235732.G46039-100000@glass.pun-pun.prv>
Tod McQuillin <devin@spamcop.net> writes:
> On Sun, 16 Sep 2001, Kovacs Baldvin wrote:
>> select NULL = NULL;
>>
>> The answer is: true!!!
> This has got to be a bug. NULL is not equal to anything (nor is it
> unequal to anything).
Indeed, this *should* yield NULL. But right now, postgres' parser
rewrites "= NULL" as "IS NULL" for compatibility with certain brain-dead
Microsoft products.
There have been several discussions on pghackers about undoing this bit
of nonstandardness, but so far nothing's been changed. See the
list archives for more detail than you really wanted.
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, devin@spamcop.net, kb136@hszk.bme.hu
Subject: Re: Intentional, or bug?
In-Reply-To: <18429.1000668667@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