Thread

1. Antw: plpgsql function gets wierd with Null parameters

   Gerhard Dieringer <dieringg@eba-haus.de> — 2000-07-03T07:42:54Z

   Skeets Norquist wrote:
   
   > When I call the following plpgsql function with the last two parameters
   > as Null, the first parameter loses it's value:
   >   ma=> select createFund('fred', null, null);
   > ...    
   > However it works fine when I give values to the last two params:
   >   ma=> select createFund('fred', 'joe', 5);
   > ...
   
   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.
   
   Gerhard
   
   
   
   

2. Re: Antw: plpgsql function gets wierd with Null parameters

   Tom Lane <tgl@sss.pgh.pa.us> — 2000-07-03T14:16:51Z

   "Gerhard Dieringer" <DieringG@eba-haus.de> 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