Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g0JHjnV43139 for ; Sat, 19 Jan 2002 12:45:49 -0500 (EST) (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 g0JHjr314217; Sat, 19 Jan 2002 12:45:53 -0500 (EST) To: chester c young cc: pgsql-sql@postgresql.org Subject: Re: null = null In-reply-to: <20020119163946.8413.qmail@web12708.mail.yahoo.com> References: <20020119163946.8413.qmail@web12708.mail.yahoo.com> Comments: In-reply-to chester c young message dated "Sat, 19 Jan 2002 08:39:46 -0800" Date: Sat, 19 Jan 2002 12:45:53 -0500 Message-ID: <14214.1011462353@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200201/238 X-Sequence-Number: 6322 chester c young writes: > the following took me by suprise: > egg=# select null=null; > ?column? > ---------- > t This is a Microsoft-compatibility kluge that is going away in the next release, or at least not being enabled by default. regression=# select version(); version --------------------------------------------------------------- PostgreSQL 7.2b5 on hppa-hp-hpux10.20, compiled by GCC 2.95.3 (1 row) regression=# select null = null; ?column? ---------- (1 row) regression=# select null IS null; ?column? ---------- t (1 row) regression=# set transform_null_equals to 1; SET VARIABLE regression=# select null = null; ?column? ---------- t (1 row) See the 7.2 docs at http://developer.postgresql.org/docs/postgres/functions-comparison.html regards, tom lane