Tom Lane wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > Agreed. I couldn't find any value to that phrase and couldn't find better
> > wording, so I removed it. Patch attached and applied.
>
> This is not an improvement.
>
> The point of the original wording is that you have to say
> RETURNS SETOF sometype
> you can't just say, eg,
> RETURNS SET
>
> Your new wording would lead the reader to the assumption that he can
> just declare a function as returning "set".
>
> Please revert the change.
I found the original confusing, as did the author, so I updated the docs
again.
--
Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Index: plpgsql.sgml
===================================================================
RCS file: /cvsroot/pgsql/doc/src/sgml/plpgsql.sgml,v
retrieving revision 1.119
diff -c -r1.119 plpgsql.sgml
*** plpgsql.sgml 28 Nov 2007 20:13:06 -0000 1.119
--- plpgsql.sgml 28 Nov 2007 20:56:17 -0000
***************
*** 132,141 ****
</para>
<para>
! <application>PL/pgSQL</> functions can also be declared to return
! a <quote>set</>, or 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>
--- 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>
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
