plpgsql is a bit tricky.
In 7.0, if an argument to a function was null, function did not execute at
all, and the result was assumed null.
In 7.1, you can control this behaviour by declaring function as 'strict'
or 'nostrict'. ex: create function(...) as '...' with (strict) gets old
behaviour, nostrict will do what you want.
On Thu, 14 Jun 2001, Jean-Michel POURE wrote:
> Hello Robert (Bob?),
>
> Thank you for your answer. I will surely make a wide use the COALESCE
> function in my scripts.
> I also noticed the same behaviour in PL/pgSQL:
>
> CREATE FUNCTION "xxxxxxxxxxxxxx" (text, text)
> RETURNS text
> AS 'BEGIN
>
> RETURN $1 || ' ' || $2;
> END;
> '
> LANGUAGE 'plpgsql'
>
> Correct me if I am wrong:
>
> It seems that a NULL value is not passed to the function ...
> ... or is it that a NULL value is not taken into account by PL/pgSQL.
>
> Thank you all for the COALESCE trick.
>
> Greetings from Jean-Michel POURE, Paris, France
> pgAdmin development team
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
>
