From 960d7ff02266b3e11684470d140ed26957aece5f Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Tue, 29 Sep 2009 20:05:29 +0000 Subject: Allow MOVE FORWARD n, MOVE BACKWARD n, MOVE FORWARD ALL, MOVE BACKWARD ALL in plpgsql. Clean up a couple of corner cases in the MOVE/FETCH syntax. Pavel Stehule --- doc/src/sgml/plpgsql.sgml | 13 ++++++++----- 1 file changed, 8 insertions(+), 5 deletions(-) (limited to 'doc/src') diff --git a/doc/src/sgml/plpgsql.sgml b/doc/src/sgml/plpgsql.sgml index f430bcfad0f..65d508c37ed 100644 --- a/doc/src/sgml/plpgsql.sgml +++ b/doc/src/sgml/plpgsql.sgml @@ -1,4 +1,4 @@ - + <application>PL/pgSQL</application> - <acronym>SQL</acronym> Procedural Language @@ -2655,16 +2655,18 @@ MOVE direction { FROM | IN } < - The options for the direction clause are - the same as for FETCH, namely + The direction clause can be any of the + variants allowed in the SQL command, namely NEXT, PRIOR, FIRST, LAST, ABSOLUTE count, RELATIVE count, - FORWARD, or - BACKWARD. + ALL, + FORWARD count | ALL , or + BACKWARD count | ALL . Omitting direction is the same as specifying NEXT. direction values that require moving @@ -2678,6 +2680,7 @@ MOVE direction { FROM | IN } < MOVE curs1; MOVE LAST FROM curs3; MOVE RELATIVE -2 FROM curs4; +MOVE FORWARD 2 FROM curs4; -- cgit v1.2.3