| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alexander Stetsenko <as(at)anapa(dot)org(dot)ru> |
| Cc: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: trouble with null |
| Date: | 2000-04-18 14:04:02 |
| Message-ID: | 19661.956066642@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
Alexander Stetsenko <as(at)anapa(dot)org(dot)ru> writes:
> I try to call such plpgsql function : do_something(int,int,date)
> All works if I call do_something(1,4,'01-01-2000');
> but if do_something(1,4,null) then inside function $1 and $2 is null
Deficiency in the function-manager design: there's only one NULL flag
for all of the inputs :-(. What's worse, if any of the inputs are NULL
then the function's result will be taken as NULL no matter what you
return!
This will require a major code overhaul to fix; it's currently planned
to happen for 7.1.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Ansley | 2000-04-18 14:06:00 | RE: DELETE FROM tableA WHERE NOT IN tableB ... |
| Previous Message | Moray McConnachie | 2000-04-18 14:00:48 | Re: DELETE FROM tableA WHERE NOT IN tableB ... |