> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> [EMAIL PROTECTED] (Anatoly K. Lasareff) writes:
>> I'afraid no. My question is: if I pass one null argument into function
>> then all other argumens, which are not null, became null inside
>> function body.
TL> Yes --- and not only that
[EMAIL PROTECTED] (Anatoly K. Lasareff) writes:
> I'afraid no. My question is: if I pass one null argument into function
> then all other argumens, which are not null, became null inside
> function body.
Yes --- and not only that, but the function's result will be taken to be
null whether you wan
include it in future releases?
GV> Regards
GV> Graham
GV> -Original Message-
GV> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
GV> Behalf Of Anatoly K. Lasareff
GV> Sent: 23 August 2000 12:46
GV> To: Tom Lane
GV> Cc: Graham Vickrage; postgresql
GV&g
uture releases?
Regards
Graham
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Anatoly K. Lasareff
Sent: 23 August 2000 12:46
To: Tom Lane
Cc: Graham Vickrage; postgresql
Subject: Re: [SQL] Null function parameters
>>>>> "TL"
> "TL" == Tom Lane <[EMAIL PROTECTED]> writes:
TL> "Graham Vickrage" <[EMAIL PROTECTED]> writes:
>> However my understanding was that if the default value is SQL NULL then any
>> values passed into the function that are null would be treated as 'NULL'.
TL> Not sure what you think you mea
"Graham Vickrage" <[EMAIL PROTECTED]> writes:
> However my understanding was that if the default value is SQL NULL then any
> values passed into the function that are null would be treated as 'NULL'.
Not sure what you think you meant by that, but a null is a null. If you
declared the table colum
