Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 613792E0160 for ; Fri, 22 Feb 2008 05:05:42 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 68045-07 for ; Fri, 22 Feb 2008 05:05:30 -0400 (AST) Received: from pih-relay06.plus.net (pih-relay06.plus.net [212.159.14.133]) by postgresql.org (Postfix) with ESMTP id 520292E0158 for ; Fri, 22 Feb 2008 05:05:30 -0400 (AST) Received: from [84.51.143.99] (helo=server3.office.archonet.com) by pih-relay06.plus.net with esmtp (Exim) id 1JSTqT-0007TM-0o; Fri, 22 Feb 2008 09:05:29 +0000 Received: from [192.168.1.36] (dell36.office.archonet.com [192.168.1.36]) by server3.office.archonet.com (Postfix) with ESMTP id B73B6274057; Fri, 22 Feb 2008 09:05:28 +0000 (GMT) Message-ID: <47BE9058.9030909@archonet.com> Date: Fri, 22 Feb 2008 09:05:28 +0000 From: Richard Huxton User-Agent: Thunderbird 2.0.0.9 (X11/20071031) MIME-Version: 1.0 To: Jyoti Seth CC: pgsql-sql@postgresql.org Subject: Re: postgresql function not accepting null values in select statement References: <001501c8752d$391c8e50$ab55aaf0$@com> In-Reply-To: <001501c8752d$391c8e50$ab55aaf0$@com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Plusnet-Relay: d415406030b01697c0e9cc2a47b51c94 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200802/159 X-Sequence-Number: 30250 Jyoti Seth wrote: > > If I pass null value as the parameter of postgresql function, which is used > in the where clause of select statement is not functioning properly. Either: 1. You're talking about frooble(), in which case it's supposed to do that. or 2. You'll need to tell us what function it is, how you're using it and what you think should happen. My guess is that you're getting a null as the result and that's not doing what you'd expect in your where clause. -- Richard Huxton Archonet Ltd