Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5GMNVa13177 for ; Sat, 16 Jun 2001 18:23:31 -0400 (EDT) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 72914; Sat, 16 Jun 2001 15:23:23 -0700 From: "Josh Berkus" Subject: Re: not null - trivial, unexpected behavior To: Peter Eisentraut , Cc: X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Sat, 16 Jun 2001 15:23:23 -0700 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200106/235 X-Sequence-Number: 3493 Peter, > Correction: Each Boolean expression can have one of *three* values: > true, > false, unknown (null). So those two sets will not be "complimentary" > in > the traditional sense because both expressions _should_ (modulo the > information I pointed you to) return "unknown". I agree pretty strongly with Peter here ... the " = NULL " functionality should go. I've already had to re-examine some of my functions for unexpected results due to = NULL possibly evaluating to TRUE, an outcome for which I did not plan. Plus it leads those new to SQL92 into trouble, as it did with John :-) -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco