Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f1CHGMx32266 for ; Mon, 12 Feb 2001 12:16:22 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [63.195.55.98] (HELO agliodbs.com) by davinci.ethosmedia.com (CommuniGate Pro SMTP 3.3) with ESMTP id 1189384 for pgsql-sql@postgresql.org; Mon, 12 Feb 2001 09:16:21 -0800 Message-ID: <3A881967.B9541E17@agliodbs.com> Date: Mon, 12 Feb 2001 09:12:07 -0800 From: Josh Berkus Reply-To: josh@agliodbs.com Organization: Aglio Database Solutions X-Mailer: Mozilla 4.73 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 CC: pgsql-sql@postgresql.org Subject: Re: plpgsql grief References: <18828.981996318@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200102/221 X-Sequence-Number: 1412 Tom, > > (and keep in mind > > that Postgres functions currently have trouble with NULLS as > > input parameters). > > Not in 7.1 they don't ... Really? Terrific. Sadly, I have 25+ PL/pgSQL functions not set up to accept NULLs ... Can you point me to (or tell me where to search) the developer notes on what improvements have been made in the function parser so that I can take advantage of them? -Josh Berkus ______AGLIO DATABASE SOLUTIONS___________________________ Josh Berkus Complete information technology josh@agliodbs.com and data management solutions (415) 565-7293 for law firms, small businesses fax 621-2533 and non-profit organizations. San Francisco