"Gerhard Dieringer" <[EMAIL PROTECTED]> 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
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);
createfund
(1 row)
However it works fine when I give values to the last two params:
ma=>