Message-ID: <3D59CE74.6010606@joeconway.com>
Date: Tue, 13 Aug 2002 20:28:52 -0700
From: Joe Conway <mail@joeconway.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.0.0) Gecko/20020530
MIME-Version: 1.0
To: Bruce Momjian <pgman@candle.pha.pa.us>
Cc: Josh Berkus <josh@agliodbs.com>, John Proctor <jproctor@prium.net>,
	Neil Conway <nconway@klamath.dyndns.org>, peter_e@gmx.net,
	tgl@sss.pgh.pa.us, pgsql-patches@postgresql.org
Subject: Re: [SQL] 16 parameter limit
References: <200208140248.g7E2mCF23367@candle.pha.pa.us>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Bruce Momjian wrote:
>>12) The biggie:  Allowing the easy return of query results from a
>>procedure.  This is currently supported through a rather difficult
>>workaround involving either the ROWTYPE datatype or a return Cursor.
>> Both approaches require the use of a procedural code loop on the
>>interface side to read the data being returned ... much clumsier than
>>just dumping the data ala PL/SQL or T-SQL.  If implemented, this rowset
>>return would the the difference between a CREATE FUNCTION and a CREATE
>>PROCEDURE statement.
> 
> 
> Done for 7.3.

Um, not done yet (PL/pgSQL table functions). Currently only SQL and C 
functions supported. I've had an off-line discussion with Neil, and I 
think he is working this item and plans to have it ready for 7.3.

CREATE PROCEDURE is not planned for 7.3 at all (I don't think; see the 
CALL foo recent discussion).

It's not clear to me which one is meant by the above. "Dumping the data 
ala PL/SQL or T-SQL" could mean either. PL/SQL supports table functions; 
T-SQL only supports the CALL foo type capability. See:
http://archives.postgresql.org/pgsql-general/2002-08/msg00602.php
for a description of the difference.

Joe