Message-ID: <3F33DFFB.7010909@joeconway.com>
Date: Fri, 08 Aug 2003 10:38:03 -0700
From: Joe Conway <mail@joeconway.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.3) Gecko/20030312
MIME-Version: 1.0
To: josh@agliodbs.com
Cc: Bruce Momjian <pgman@candle.pha.pa.us>,
	PostgreSQL-development <pgsql-hackers@postgresql.org>
Subject: Re: TODO items
References: <200308081713.h78HD6h00928@candle.pha.pa.us>
	<200308081022.22741.josh@agliodbs.com>
In-Reply-To: <200308081022.22741.josh@agliodbs.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Josh Berkus wrote:
>>>Actually, now that I look at it again, it is referring to procedures, 
>>>not functions. Maybe just make it:
>>>
>>>o Add capability to create and call PROCEDURES
> 
> OK.   I need to put a full proposal behind this once 7.4 is in the can.  
> However, this is largely academic until we get someone who really wants to 
> take ownership of PL/pgSQL and has the coding skills (I have the former but 
> not the latter).  
> 

This isn't isolated to just PL/pgSQL, just like the ability to create 
and call functions isn't. Support for PROCEDUREs in the backend is a 
prerequisite to being able to use PL/pgSQL to create procedures. It is 
necessary but not sufficient.

Similarly, if we want to support IN/OUT or named parameters, it isn't a 
PL/pgSQL issue per se, it is a general one.

Joe