Received: from sss.pgh.pa.us (sss.pgh.pa.us [216.151.103.158]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4FEE3A21484 for ; Tue, 15 May 2001 10:14:04 -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.3/8.11.3) with ESMTP id f4FECgR01159; Tue, 15 May 2001 10:12:42 -0400 (EDT) To: Guru Prasad cc: "pgsql-sql@postgresql.org" Subject: Re: How NULL is interpreted in Pgsql In-reply-to: References: Comments: In-reply-to Guru Prasad message dated "Tue, 15 May 2001 13:38:17 +0530" Date: Tue, 15 May 2001 10:12:42 -0400 Message-ID: <1156.989935962@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200105/147 X-Sequence-Number: 2964 Guru Prasad writes: > 'select * from junk where id != 11'; > To my surprise, it displayed all the records except those which had > 'NULL' in the 'id' field. This is correct per spec: NULL is not a value and it doesn't act like one. See any discussion of SQL NULLs --- Bruce's book talks about this IIRC, or we've been over the turf more than once in the mailing list archives. regards, tom lane