Re: Antw: plpgsql function gets wierd with Null parameters

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Gerhard Dieringer" <DieringG(at)eba-haus(dot)de>
Cc: pgsql-sql(at)postgresql(dot)org, "<Skeets and Kim Norquist" <norqu2(at)juno(dot)com>
Subject: Re: Antw: plpgsql function gets wierd with Null parameters
Date: 2000-07-03 14:16:51
Message-ID: 18923.962633811@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-sql

"Gerhard Dieringer" <DieringG(at)eba-haus(dot)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

In response to

Browse pgsql-sql by date

  From Date Subject
Next Message emils 2000-07-03 14:40:37
Previous Message Grant Finnemore 2000-07-03 09:34:46 Re: trigger or something else?