Re: Bogus reporting of non-null value in function call.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James(at)VolumeFour(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Bogus reporting of non-null value in function call.
Date: 2000-04-24 22:56:56
Message-ID: 2250.956617016@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

"James Finch" <James(at)VolumeFour(dot)com> writes:
> Arguments to a function seem to be incorrectly validated against constraints
> on the table on which it operates.

I think what's really going on here is that because the function manager
interface defines only one isNull flag for a function call, *all* the
parameters appear to be NULL if any one of them is actually NULL.
(What's more, the function result will be taken to be NULL no matter
what you return.)

Fixing this is on the to-do list for 7.1. It's not a trivial fix
because so much code will have to be touched in order to change
that interface :-(

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jim Buckley 2000-04-25 02:53:37 initdb crash after install
Previous Message James Finch 2000-04-24 22:45:16 RE: Bogus reporting of non-null value in function call.