From: Deirdre Hall <d.hall@delcan.com>
To: pgsql-sql@postgresql.org
Subject: Stored function not accepting null value?
Date: Wed, 1 Apr 2009 13:17:30 -0500 (CDT)
Message-ID: <03f401c9b2f6$a3c2ee90$5062140a@dc06012008> (raw)
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.
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: d.hall@delcan.com
Subject: Re: Stored function not accepting null value?
In-Reply-To: <03f401c9b2f6$a3c2ee90$5062140a@dc06012008>
* 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