From: | Guillaume Lelarge <guillaume(at)lelarge(dot)info> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-docs(at)postgresql(dot)org |
Subject: | Re: Two fixes for plpgsql.sgml |
Date: | 2007-11-28 22:42:16 |
Message-ID: | 474DEEC8.80502@lelarge.info |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Bruce Momjian a écrit :
> Alvaro Herrera wrote:
>>[...]
>> The point of "any datatype they can return a single instance of" is that
>> this can be a set of scalar values (e.g. "RETURNS SETOF int") or of a
>> complex type ("RETURNS SETOF table"), or anything else they can return a
>> single instance of :-P (SETOF anyelement? SETOF table%TYPE?)
>
> Good idea, updated:
>
> <application>PL/pgSQL</> functions can also be declared to return
> a <quote>set</> (or table) of any data type that can be returned as
> a single instance. Such a function generates its output by executing
> <command>RETURN NEXT</> for each desired element of the result
> set, or by using <command>RETURN QUERY</> to output the result of
> evaluating a query.
>
Great. Now I better understand this part. Thank you all.
--
Guillaume.
http://www.postgresqlfr.org
http://dalibo.com
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2007-11-29 00:53:34 | Re: Partition: use triggers instead of rules |
Previous Message | Bruce Momjian | 2007-11-28 22:36:21 | Re: PITR Doc clarifications |