BACKWARD>.
Omitting direction is the same
as specifying NEXT>.
+ In the forms using a count,
+ the count can be any integer-valued
+ expression (unlike the SQL FETCH command,
+ which only allows an integer constant).
direction values that require moving
backward are likely to fail unless the cursor was declared or opened
with the SCROLL> option.
be checked to see whether there was a next row to move to.
- The direction clause can be any of the
- variants allowed in the SQL
- command, namely
- NEXT>,
- PRIOR>,
- FIRST>,
- LAST>,
- ABSOLUTE> count,
- RELATIVE> count,
- ALL>,
- FORWARD> count | ALL> , or
- BACKWARD> count | ALL> .
- Omitting direction is the same
- as specifying NEXT>.
- direction values that require moving
- backward are likely to fail unless the cursor was declared or opened
- with the SCROLL> option.
-
-
Examples: