Re: [SQL] 16 parameter limit - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: [SQL] 16 parameter limit
Date
Msg-id 200208140336.g7E3a4e25289@candle.pha.pa.us
Whole thread Raw
In response to Re: [SQL] 16 parameter limit  (Joe Conway <mail@joeconway.com>)
List pgsql-patches
Joe Conway wrote:
> 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.

OK, added to 7.3 open items:

    Allow PL/PgSQL functions to return sets

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

Right, on TODO.

> 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.

Not sure.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 359-1001
  +  If your life is a hard drive,     |  13 Roberts Road
  +  Christ can be your backup.        |  Newtown Square, Pennsylvania 19073

pgsql-patches by date:

Previous
From: Joe Conway
Date:
Subject: Re: [SQL] 16 parameter limit
Next
From: Bruce Momjian
Date:
Subject: Re: Documentation update (pg_get_fkeydef, current_database)