Received: from www-uk-05.digiserve.com ([195.97.231.11]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f338YGK35205 for ; Tue, 3 Apr 2001 04:34:16 -0400 (EDT) (envelope-from dev@archonet.com) Received: from mainbox.archonet.com (mwynhau.demon.co.uk [193.237.186.96]) by www-uk-05.digiserve.com (8.9.1/8.9.1) with ESMTP id JAA07845; Tue, 3 Apr 2001 09:35:08 +0100 (BST) Received: from client (client.archonet.com [192.168.1.16]) by mainbox.archonet.com (Postfix) with SMTP id 42B192A3AB; Tue, 3 Apr 2001 09:05:36 +0100 (BST) Message-ID: <00a701c0bc14$dc4bd920$1001a8c0@archonet.com> From: "Richard Huxton" To: "Picard, Cyril" , References: Subject: Re: passing null parameter to plpgsq functions Date: Tue, 3 Apr 2001 09:05:32 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="Windows-1252" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200104/24 X-Sequence-Number: 2363 From: "Picard, Cyril" > Hello > I wrote a plpgsql function with few parameters ; when I call the function, > some of the parameters can be null. > In this case, all the parameters are considered as null in the function's > body ! is it a feature ? how can I work around this ? It's a feature in versions before 7.1 (or possibly 7.0.x) you can still get that behaviour in 7.1 by asking for strict null handling on a specific function. The only remedy AFAIK is to upgrade. - Richard Huxton