1
0
mirror of https://github.com/postgres/postgres.git synced 2025-07-28 23:42:10 +03:00

Here's a patch to do the following:

1. Rename spi_return_next to return_next.
2. Add a new test for return_next.
3. Update the expected output.
4. Update the documentation.

Abhijit Menon-Sen
This commit is contained in:
Bruce Momjian
2005-06-05 03:16:42 +00:00
parent 27bdb0c40d
commit bebe7c5600
5 changed files with 55 additions and 57 deletions

View File

@ -1,5 +1,5 @@
<!--
$PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.40 2005/05/20 01:52:24 neilc Exp $
$PostgreSQL: pgsql/doc/src/sgml/plperl.sgml,v 2.41 2005/06/05 03:16:29 momjian Exp $
-->
<chapter id="plperl">
@ -182,8 +182,11 @@ $$ LANGUAGE plperl;
SELECT * FROM perl_set();
</programlisting>
Note that when you do this, Perl will have to build the entire array in
memory; therefore the technique does not scale to very large result sets.
When you do this, Perl will have to build the entire array in memory;
therefore the technique does not scale to very large result sets. You
can instead call <function>return_next</function> for each element of
the result set, passing it either a scalar or a reference to a hash,
as appropriate to your function's return type.
</para>
<para>