Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id JAA55400 for ; Tue, 31 Aug 1999 09:31:58 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id JAA15132; Tue, 31 Aug 1999 09:31:23 -0400 (EDT) To: holm@freibergnet.de cc: pgsql-sql@postgreSQL.org Subject: Re: [SQL] problem with select In-reply-to: Your message of Tue, 31 Aug 1999 08:29:20 +0200 <19990831082920.A23046@pegasus.freibergnet.de> Date: Tue, 31 Aug 1999 09:31:23 -0400 Message-ID: <15130.936106283@sss.pgh.pa.us> From: Tom Lane Holm Tiffe writes: > It is almost working, my database isn't that big that memory becomes a > problem; the machine has 512MB. > But why is nothing found if one value of a column contains NULL ? Because nulls propagate: any operator whose input is NULL produces NULL. The only things that don't return NULL are the special syntaxes IS NULL, IS NOT NULL, and CASE expressions using them (in particular the CASE shortcuts COALESCE, etc). You probably want to write COALESCE(field, '') in place of just field for any column that can be NULL. regards, tom lane