Received: from web12708.mail.yahoo.com (web12708.mail.yahoo.com [216.136.173.245]) by postgresql.org (8.11.3/8.11.4) with SMTP id g0JGdfV36916 for ; Sat, 19 Jan 2002 11:39:41 -0500 (EST) (envelope-from chestercyoung@yahoo.com) Message-ID: <20020119163946.8413.qmail@web12708.mail.yahoo.com> Received: from [207.188.162.30] by web12708.mail.yahoo.com via HTTP; Sat, 19 Jan 2002 08:39:46 PST Date: Sat, 19 Jan 2002 08:39:46 -0800 (PST) From: chester c young Subject: null = null To: pgsql-sql@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200201/236 X-Sequence-Number: 6320 the following took me by suprise: egg=# select null=null; ?column? ---------- t if this were true, for example, then only one null key could be in a unique index, which is certainly not true. i thought the philosphical idea behind null in SQL was you didn't know, which can't have equivalence (as versus the pragmatic idea in C where null is a dead end pointer, which can have equivalence). or have I been too involved with my Oracle databases? __________________________________________________ Do You Yahoo!? Send FREE video emails in Yahoo! Mail! http://promo.yahoo.com/videomail/