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

"James Finch" <James@VolumeFour.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