Received: from POP3.tu-dresden.de (POP3.tu-dresden.de [141.30.2.83]) by hub.org (8.10.1/8.10.1) with SMTP id e8HKZWs63303; Sun, 17 Sep 2000 16:35:32 -0400 (EDT) Received: from rmail.urz.tu-dresden.de by rks3 with SMTP (PP); Sun, 17 Sep 2000 22:30:08 +0200 Received: from [192.168.100.2] (actually RDIAL715.urz.tu-dresden.de) by rmail with SMTP (IC-PP); Sun, 17 Sep 2000 22:33:28 +0200 Date: Sun, 17 Sep 2000 22:37:35 +0200 (CEST) From: Peter Eisentraut X-Sender: peter@peter To: Joel Burton cc: pgsql-general@postgreSQL.org, pgsql-sql@postgreSQL.org Subject: Re: All function parameters become NULL if one is? In-Reply-To: <200009162247.e8GMlan28506@olympus.scw.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Archive-Number: 200009/442 Joel Burton writes: > I have a function that takes two text parameters. If both of these > are non-null, everything works fine. However, if one of these two > parameters is null and one is not, the function receives both as null. Worse, no matter what the function does, the return value is also null. > Is this intentional? Is there a way around this? Wait for 7.1. -- Peter Eisentraut peter_e@gmx.net http://yi.org/peter-e/