From ad9a99c24f7084d2511e84efbac3a807b14656f3 Mon Sep 17 00:00:00 2001
From: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu, 5 Jul 2007 19:15:12 +0000
Subject: [PATCH] Improve description of SPI_scroll_cursor_move's return
values, per a gripe by Pavel Stehule awhile ago.
---
doc/src/sgml/spi.sgml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/doc/src/sgml/spi.sgml b/doc/src/sgml/spi.sgml
index aaec698bcf4..a875d8585bb 100644
--- a/doc/src/sgml/spi.sgml
+++ b/doc/src/sgml/spi.sgml
@@ -1,4 +1,4 @@
-<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.57 2007/05/03 15:05:56 neilc Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.58 2007/07/05 19:15:12 tgl Exp $ -->
<chapter id="spi">
<title>Server Programming Interface</title>
@@ -1832,9 +1832,10 @@ void SPI_scroll_cursor_move(Portal <parameter>portal</parameter>, FetchDirection
<title>Return Value</title>
<para>
- <varname>SPI_processed</varname> and
- <varname>SPI_tuptable</varname> are set as in
+ <varname>SPI_processed</varname> is set as in
<function>SPI_execute</function> if successful.
+ <varname>SPI_tuptable</varname> is set to <symbol>NULL</>, since
+ no rows are returned by this function.
</para>
</refsect1>
--
GitLab