Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.9.3/8.9.3) with ESMTP id KAA26942 for ; Tue, 18 Apr 2000 10:04:29 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss2.sss.pgh.pa.us (8.9.3/8.9.3) with ESMTP id KAA19664; Tue, 18 Apr 2000 10:04:02 -0400 (EDT) To: Alexander Stetsenko cc: pgsql-sql@postgresql.org Subject: Re: trouble with null In-reply-to: <38FC193D.ED1289B8@anapa.org.ru> References: <38FC193D.ED1289B8@anapa.org.ru> Comments: In-reply-to Alexander Stetsenko message dated "Tue, 18 Apr 2000 12:13:49 +0400" Date: Tue, 18 Apr 2000 10:04:02 -0400 Message-ID: <19661.956066642@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200004/181 Alexander Stetsenko writes: > I try to call such plpgsql function : do_something(int,int,date) > All works if I call do_something(1,4,'01-01-2000'); > but if do_something(1,4,null) then inside function $1 and $2 is null Deficiency in the function-manager design: there's only one NULL flag for all of the inputs :-(. What's worse, if any of the inputs are NULL then the function's result will be taken as NULL no matter what you return! This will require a major code overhaul to fix; it's currently planned to happen for 7.1. regards, tom lane