diff options
| author | Tom Lane | 2018-07-12 16:28:43 +0000 |
|---|---|---|
| committer | Tom Lane | 2018-07-12 16:28:43 +0000 |
| commit | 2e7a25c1dcb7acb9d1138934cade1f1a7e6fe690 (patch) | |
| tree | b7bdcc866060def3a9fa6445ff905496a2d9c0bf /doc/src | |
| parent | e8fe3bb23003028760948f829f7a701cdd66dbf2 (diff) | |
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
Diffstat (limited to 'doc/src')
| -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 dd051f3f755..a84710f37e8 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -3033,6 +3033,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. @@ -3071,26 +3075,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 cc49b6f0ce6..c38cf03e028 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> |