Skip site navigation (1) Skip section navigation (2)

Re: Two fixes for plpgsql.sgml

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Guillaume Lelarge <guillaume(at)lelarge(dot)info>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-docs(at)postgresql(dot)org
Subject: Re: Two fixes for plpgsql.sgml
Date: 2007-11-28 21:40:36
Message-ID: 20071128214036.GW5118@alvh.no-ip.org (view raw or flat)
Thread:
Lists: pgsql-docs
Bruce Momjian wrote:

> --- 132,142 ----
>       </para>
>   
>       <para>
> !      <application>PL/pgSQL</> functions can also be declared to return a
> !      group of values, either as a single row, or a group of rows, like a
> !      table.  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.
>       </para>

Hmm, ISTM the correct terminology is "set of rows".  I have never heard
of "a group of rows".  It seems to me the easiest way out of the problem
would have been substituting the commas in the original with parens:

     <application>PL/pgSQL</> functions can also be declared to return
     a <quote>set</> (or <quote>table</>) of any data type they can return a single
     instance of.

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?)

-- 
Alvaro Herrera                               http://www.PlanetPostgreSQL.org/
"World domination is proceeding according to plan"        (Andrew Morton)

In response to

Responses

pgsql-docs by date

Next:From: Bruce MomjianDate: 2007-11-28 21:47:59
Subject: Re: Two fixes for plpgsql.sgml
Previous:From: Joshua D. DrakeDate: 2007-11-28 21:03:42
Subject: Re: [PATCHES] Partition: use triggers instead of rules

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group