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 e63EGtS08888 for ; Mon, 3 Jul 2000 10:16:55 -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 KAA18926; Mon, 3 Jul 2000 10:16:51 -0400 (EDT) To: "Gerhard Dieringer" cc: pgsql-sql@postgresql.org, " Subject: Re: Antw: plpgsql function gets wierd with Null parameters In-reply-to: References: Comments: In-reply-to "Gerhard Dieringer" message dated "Mon, 03 Jul 2000 09:42:54 +0200" Date: Mon, 03 Jul 2000 10:16:51 -0400 Message-ID: <18923.962633811@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200007/16 "Gerhard Dieringer" writes: > It's a known bug of plpgsql that if one arg is NULL, all other args > are also assumed to be NULL. I think (hope) this will be fixed in a > future version. 7.1. It is already fixed in current development sources. BTW it's not actually plpgsql's fault, but that of the function-call interface. The problem appears no matter what programming language you write the function in. regards, tom lane