Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id f8GJVZ725504 for ; Sun, 16 Sep 2001 15:31:35 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f8GJV7K18432; Sun, 16 Sep 2001 15:31:07 -0400 (EDT) To: Tod McQuillin cc: Kovacs Baldvin , pgsql-sql@postgresql.org Subject: Re: Intentional, or bug? In-reply-to: <20010916235732.G46039-100000@glass.pun-pun.prv> References: <20010916235732.G46039-100000@glass.pun-pun.prv> Comments: In-reply-to Tod McQuillin message dated "Mon, 17 Sep 2001 00:04:02 +0900" Date: Sun, 16 Sep 2001 15:31:07 -0400 Message-ID: <18429.1000668667@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200109/93 X-Sequence-Number: 4757 Tod McQuillin 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