Re: Stored function not accepting null value? - Mailing list pgsql-sql

From Tom Lane
Subject Re: Stored function not accepting null value?
Date
Msg-id 10034.1238612469@sss.pgh.pa.us
Whole thread Raw
In response to Stored function not accepting null value?  ("Deirdre Hall" <d.hall@delcan.com>)
Responses Re: Stored function not accepting null value?  ("Deirdre Hall" <d.hall@delcan.com>)
List pgsql-sql
"Deirdre Hall" <d.hall@delcan.com> writes:
> I am using a stored function to determine whether a table needs an update
> or insert, based on the merge_db function in the postgres documentation.
> (Not currently including it below because it's rather long, but other than
> the fact that it contains 27 values, it's pretty much the same as that
> example.)

Well, not including it is a good way to ensure that no one will really
know what the problem is ... but I wonder whether you declared the
function STRICT.  That'd prevent it from being called with a NULL
argument, which seems to fit the reported behavior.
        regards, tom lane


pgsql-sql by date:

Previous
From: "Deirdre Hall"
Date:
Subject: Stored function not accepting null value?
Next
From: "Deirdre Hall"
Date:
Subject: Re: Stored function not accepting null value?