Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Commitad9a99c

Browse files
committed
Improve description of SPI_scroll_cursor_move's return values, per a
gripe by Pavel Stehule awhile ago.
1 parent83aaebb commitad9a99c

File tree

1 file changed

+4
-3
lines changed

1 file changed

+4
-3
lines changed

‎doc/src/sgml/spi.sgml

Lines changed: 4 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.57 2007/05/0315:05:56 neilc Exp $ -->
1+
<!-- $PostgreSQL: pgsql/doc/src/sgml/spi.sgml,v 1.58 2007/07/05 19:15:12 tgl Exp $ -->
22

33
<chapter id="spi">
44
<title>Server Programming Interface</title>
@@ -1832,9 +1832,10 @@ void SPI_scroll_cursor_move(Portal <parameter>portal</parameter>, FetchDirection
18321832
<title>Return Value</title>
18331833

18341834
<para>
1835-
<varname>SPI_processed</varname> and
1836-
<varname>SPI_tuptable</varname> are set as in
1835+
<varname>SPI_processed</varname> is set as in
18371836
<function>SPI_execute</function> if successful.
1837+
<varname>SPI_tuptable</varname> is set to <symbol>NULL</>, since
1838+
no rows are returned by this function.
18381839
</para>
18391840
</refsect1>
18401841

0 commit comments

Comments
 (0)

[8]ページ先頭

©2009-2025 Movatter.jp