Antw: plpgsql function gets wierd with Null parameters

From: "Gerhard Dieringer" <DieringG(at)eba-haus(dot)de>
To: <pgsql-sql(at)postgresql(dot)org>
Cc: "<Skeets and Kim Norquist" <norqu2(at)juno(dot)com>
Subject: Antw: plpgsql function gets wierd with Null parameters
Date: 2000-07-03 07:42:54
Message-ID: s960603b.071@kopo001
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql


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

Responses

Browse pgsql-sql by date

  From Date Subject
Next Message Grant Finnemore 2000-07-03 09:34:46 Re: trigger or something else?
Previous Message tjk@tksoft.com 2000-07-03 06:58:39 Re: case insensitive search