From: Tom Lane <tgl@sss.pgh.pa.us>
To: Deirdre Hall <d.hall@delcan.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Stored function not accepting null value?
Date: Wed, 01 Apr 2009 15:01:09 -0400
Message-ID: <10034.1238612469@sss.pgh.pa.us> (raw)
In-Reply-To: <03f401c9b2f6$a3c2ee90$5062140a@dc06012008>
References: <03f401c9b2f6$a3c2ee90$5062140a@dc06012008>
"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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, d.hall@delcan.com
Subject: Re: Stored function not accepting null value?
In-Reply-To: <10034.1238612469@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox