Bug in how nulls are handled by plpgsql?

From: "Jonathan Ellis" <jellis(at)advocast(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Bug in how nulls are handled by plpgsql?
Date: 2000-11-06 17:53:12
Message-ID: 055301c0481a$6eb55120$0d00a8c0@dsl.inconnect.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

bf2=# create function foo (varchar, varchar) returns varchar as '
begin
return $1;
end;
' language 'plpgsql';

bf2'# bf2'# bf2'# bf2'# CREATE
bf2=# bf2=# select foo('asdf', null) from dual;
foo
-----

(1 row)

Even though the function foo never references the null, apparently postgres
thinks, "oh, a function call with a null in it. Must be null." and doesn't
even bother executing the function. Bug?

On another null-related note, is there any way to make
select 'asdf' || null from dual

return 'asdf' without changing it to
select 'asdf' || coalesce(null, '') from dual

?

-Jonathan

Responses

Browse pgsql-general by date

  From Date Subject
Next Message michel_climber 2000-11-06 18:16:15 Images
Previous Message Jonathan Arrien 2000-11-06 17:04:59 initdb