Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f0G4wx038676 for ; Mon, 15 Jan 2001 23:59:00 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id f0G4wpJ02642; Mon, 15 Jan 2001 23:58:51 -0500 (EST) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: Question #4 about PL/PGSQL In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 15 Jan 2001 19:10:14 -0800" Date: Mon, 15 Jan 2001 23:58:51 -0500 Message-ID: <2639.979621131@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200101/158 X-Sequence-Number: 819 "Josh Berkus" writes: > 4. If I pass a NULL to any of the parameters of a PL/PGSQL > function, any (other) VARCHAR parameters are set to NULL as > well. Not only varchar --- any other parameters, period. And not only that, but the result is taken as NULL no matter what you try to return. This is a longstanding deficiency that is fixed by the new function manager in 7.1. regards, tom lane