From: | "Vazsonyi Peter[ke]" <neko(at)kornel(dot)szif(dot)hu> |
---|---|
To: | hackers(at)postgreSQL(dot)org |
Subject: | Re: [HACKERS] NULL handling question |
Date: | 1999-03-29 17:32:43 |
Message-ID: | Pine.A32.4.05.9903291804500.16770-100000@kornel.szif.hu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 29 Mar 1999, Thomas Lockhart wrote:
> Postgres assumes that a NULL input will give a NULL output,
But why? That is not true in all case, i mean so like: "FALSE && dont'know"
is always FALSE.
> and never calls your routine at all.
But! I see the output of elogs in function.
I don't sure about 6.5, i test it not for a long time. The 6.4.x calls my
functions always (with one or more NULL parameters).
Then if the return value has "pass-by-reference" type, can i give a NULL or
a NOT NULL value. I don't now realy, but i think it's posible to give NULL
indicator with int4, bool, etc like type results.
I mean this feature is necessary... Not? ;)
Any opinion?
So thans for all.
--
NeKo@(kva.hu|Kornel.szif.hu) the servant of Crash
hu:http://lsc.kva.hu en:-- (sorry, my english is...)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-03-29 17:40:17 | Re: [HACKERS] Memory grows without bounds in aggregates! |
Previous Message | Thomas Lockhart | 1999-03-29 17:31:53 | Re: [HACKERS] Parser doesn't grok unqualified array element |