Received: from rakete.joerdens.de ([62.104.116.200]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f21IGtx70605 for ; Thu, 1 Mar 2001 13:16:56 -0500 (EST) (envelope-from frank@rakete.joerdens.de) Received: (from frank@localhost) by rakete.joerdens.de (8.9.3/8.9.3) id TAA12432 for pgsql-sql@postgresql.org; Thu, 1 Mar 2001 19:16:54 +0100 Date: Thu, 1 Mar 2001 19:16:54 +0100 From: Frank Joerdens To: pgsql-sql@postgresql.org Subject: Weird NOT IN effect with NULL values Message-ID: <20010301191654.A12406@rakete.joerdens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i X-Subliminal-Message: Use Linux! Use Linux! X-Archive-Number: 200103/8 X-Sequence-Number: 1649 When doing a subselect with NOT IN, as in SELECT name FROM customer WHERE customer_id NOT IN ( SELECT customer_id FROM salesorder ); (from Bruce Momjian's book) I get no rows if the result column returned by the subselect contains NULL values. It works as expected if I remove the NULL values from the result set. Is this behaviour correct and if so, why? I am using 7.1 beta 4. Regards, Frank