Received: from web10006.mail.yahoo.com (web10006.mail.yahoo.com [216.136.130.42]) by postgresql.org (8.11.3/8.11.1) with SMTP id f5GFGKa61927 for ; Sat, 16 Jun 2001 11:16:20 -0400 (EDT) (envelope-from jmscott@yahoo.com) Message-ID: <20010616151611.40654.qmail@web10006.mail.yahoo.com> Received: from [207.168.117.52] by web10006.mail.yahoo.com; Sat, 16 Jun 2001 08:16:11 PDT Date: Sat, 16 Jun 2001 08:16:11 -0700 (PDT) From: John Scott Reply-To: john@august.com Subject: not null - trivial, unexpected behavior To: pgsql-sql@postgresql.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Archive-Number: 200106/228 X-Sequence-Number: 3486 the following behaviour seems inconsistent to me. I can qualify on nulls, but not on nonullness. This was tested under 7.1.2 create table A ( a text, b text ); insert into A(a) values('a1'); insert into A(a, b) values('a2', 'b2'); select count(*) from A where b = null; /* Returns 1, ok */ select count(*) from A where b != null; /* Returns 0 ... not ok! */ What am i missing? Shouldn't those two sets be complimentary? john ===== John Scott Senior Partner August Associates email: john@august.com web: http://www.august.com/~jmscott __________________________________________________ Do You Yahoo!? Spot the hottest trends in music, movies, and more. http://buzz.yahoo.com/