diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-07-12 12:28:43 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-07-12 12:28:43 -0400 |
| commit | b4900835d63cf0c56ab97b7b666d6407d3d98c22 (patch) | |
| tree | 3127c3696b1e900b8f43556c8a9a1aeb8b64032d | |
| parent | 19648375cc307eb5849906c0ddef737ddacf141a (diff) | |
| download | postgresql-b4900835d63cf0c56ab97b7b666d6407d3d98c22.tar.gz | |
Doc: minor improvement in pl/pgsql FETCH/MOVE documentation.
Explain that you can use any integer expression for the "count" in
pl/pgsql's versions of FETCH/MOVE, unlike the SQL versions which only
allow a constant.
Remove the duplicate version of this para under MOVE. I don't see
a good reason to maintain two identical paras when we just said that
MOVE works exactly like FETCH.
Per Pavel Stehule, though I didn't use his text.
Discussion: https://postgr.es/m/CAFj8pRAcvSXcNdUGx43bOK1e3NNPbQny7neoTLN42af+8MYWEA@mail.gmail.com
| -rw-r--r-- | doc/src/sgml/plpgsql.sgml | 24 | ||||
| -rw-r--r-- | doc/src/sgml/ref/fetch.sgml | 2 |
2 files changed, 5 insertions, 21 deletions
diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index 8165e9bac2..cf564b3f37 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -3173,6 +3173,10 @@ FETCH <optional> <replaceable>direction</replaceable> { FROM | IN } </optional> <literal>BACKWARD</>. Omitting <replaceable>direction</replaceable> is the same as specifying <literal>NEXT</>. + In the forms using a <replaceable>count</replaceable>, + the <replaceable>count</replaceable> can be any integer-valued + expression (unlike the SQL <command>FETCH</command> command, + which only allows an integer constant). <replaceable>direction</replaceable> values that require moving backward are likely to fail unless the cursor was declared or opened with the <literal>SCROLL</> option. @@ -3211,26 +3215,6 @@ MOVE <optional> <replaceable>direction</replaceable> { FROM | IN } </optional> < </para> <para> - The <replaceable>direction</replaceable> clause can be any of the - variants allowed in the SQL <xref linkend="sql-fetch"> - command, namely - <literal>NEXT</>, - <literal>PRIOR</>, - <literal>FIRST</>, - <literal>LAST</>, - <literal>ABSOLUTE</> <replaceable>count</replaceable>, - <literal>RELATIVE</> <replaceable>count</replaceable>, - <literal>ALL</>, - <literal>FORWARD</> <optional> <replaceable>count</replaceable> | <literal>ALL</> </optional>, or - <literal>BACKWARD</> <optional> <replaceable>count</replaceable> | <literal>ALL</> </optional>. - Omitting <replaceable>direction</replaceable> is the same - as specifying <literal>NEXT</>. - <replaceable>direction</replaceable> values that require moving - backward are likely to fail unless the cursor was declared or opened - with the <literal>SCROLL</> option. - </para> - - <para> Examples: <programlisting> MOVE curs1; diff --git a/doc/src/sgml/ref/fetch.sgml b/doc/src/sgml/ref/fetch.sgml index 24c8c49156..d8784e537f 100644 --- a/doc/src/sgml/ref/fetch.sgml +++ b/doc/src/sgml/ref/fetch.sgml @@ -99,7 +99,7 @@ FETCH [ <replaceable class="PARAMETER">direction</replaceable> [ FROM | IN ] ] < This page describes usage of cursors at the SQL command level. If you are trying to use cursors inside a <application>PL/pgSQL</> function, the rules are different — - see <xref linkend="plpgsql-cursors">. + see <xref linkend="plpgsql-cursor-using">. </para> </note> </refsect1> |