[SQL] Stored function not accepting null value?
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.) It works fine as long as all the values are defined: select event_archive (7, 2, 2, 2, 3, text 'TIMS', 3, text 'I-90', 2, 3, 1.2, 1.3, 3, 1, 2, text 'important', timestamp '2008-01-01', timestamp '2008-01-01', timestamp '2008-01-01', timestamp '2008-01-01', timestamp '2008-01-01', text '2 hours', timestamp '2008-01-01', timestamp '2008-01-01', text 'oak', text 'main', 2); but if I change any of the above values to null, the function simply doesn't operate. select event_archive (7, 2, 2, 2, 3, text 'TIMS', 3, text 'I-90', 2, 3, 1.2, 1.3, 3, 1, 2, text 'important', timestamp '2008-01-01', timestamp '2008-01-01', timestamp '2008-01-01', timestamp '2008-01-01', timestamp '2008-01-01', text '2 hours', timestamp '2008-01-01', timestamp '2008-01-01', text 'oak', text 'main', null); It returns: Total query runtime: 0 ms. 1 rows retrieved. versus a runtime of about 13ms when it successfully updates or inserts. I put raise notices into the function to try to debug, and it never even hits the first one in the first LOOP when there is a null value. The only column in the table that is declared not null would be the 7 in the above statement (id), all other fields should be able to accept a null value. Is this a known limitation with functions, or am I doing something incorrectly? Thanks, DHall This communication may contain information that is confidential, privileged or subject to copyright. If you are not the intended recipient, please advise by return e-mail and delete the message and any attachments immediately without reading, copying or forwarding to others.
Re: [SQL] Stored function not accepting null value?
Deirdre Hall d.h...@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 -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
Re: [SQL] Stored function not accepting null value?
And that would be where I went wrong. Thanks. DHall -Original Message- From: Tom Lane [mailto:t...@sss.pgh.pa.us] Sent: Wednesday, April 01, 2009 2:01 PM To: Deirdre Hall Cc: pgsql-sql@postgresql.org Subject: Re: [SQL] Stored function not accepting null value? Deirdre Hall d.h...@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 This communication may contain information that is confidential, privileged or subject to copyright. If you are not the intended recipient, please advise by return e-mail and delete the message and any attachments immediately without reading, copying or forwarding to others. -- Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-sql
