Received: from sss2.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2]) by hub.org (8.10.1/8.10.1) with ESMTP id e7NE1fN17390 for ; Wed, 23 Aug 2000 10:01:41 -0400 (EDT) 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 KAA27710; Wed, 23 Aug 2000 10:00:59 -0400 (EDT) To: tolik@aaanet.ru (Anatoly K. Lasareff) cc: "Graham Vickrage" , "postgresql" Subject: Re: Null function parameters In-reply-to: <86em3gumhr.fsf@tolikus.hq.aaanet.ru> References: <86em3gumhr.fsf@tolikus.hq.aaanet.ru> Comments: In-reply-to tolik@aaanet.ru (Anatoly K. Lasareff) message dated "23 Aug 2000 17:37:36 +0400" Date: Wed, 23 Aug 2000 10:00:59 -0400 Message-ID: <27707.967039259@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200008/246 tolik@aaanet.ru (Anatoly K. Lasareff) writes: > I'afraid no. My question is: if I pass one null argument into function > then all other argumens, which are not null, became null inside > function body. Yes --- and not only that, but the function's result will be taken to be null whether you want it to be or not. This has been gone over *many* times before on this mail list, so I didn't think I needed to repeat it. This will be fixed in 7.1 (is already fixed in current sources). regards, tom lane