SQL/MX 2.x Query Guide (G06.24+, H06.03+)

Operators and Operator Groups
HP NonStop SQL/MX Query Guide—523728-003
7-6
CURSOR_UPDATE Operator
The example of the CURSOR_DELETE operator is based on:
DELETE FROM bbase WHERE unique1 < 32000;
. . 8 cursor_delete
part_key_predicates:
(indexcol(\TESTSYS.$BIG18A.WISC32M.IXB4.UNIQUE3) =
indexcol(\TESTSYS.$BIG18A.WISC32M.BBASE.UNIQUE3))
begin_key: (indexcol(\TESTSYS.$BIG18A.WISC32M.IXB4.UNIQUE3) =
indexcol(\TESTSYS.$BIG18A.WISC32M.BBASE.UNIQUE3))
CURSOR_UPDATE Operator
DAM Unique Group
The CURSOR_UPDATE operator describes a portion of an execution plan that works
on one row only. The CURSOR_UPDATE operation is performed by first retrieving
rows from the table and then updating each row that is required. This operation differs
from SUBSET_UPDATE, in which the read and update are performed in a combined
operation.
The CURSOR_UPDATE operator has no child nodes. The description field for this
operator contains:
The example of the CURSOR_UPDATE operator is based on:
UPDATE abase SET two = two + 1 WHERE unique3 < 32000;
. . 4 cursor_update
new_rec_expr: (\TESTSYS.$BIG18A.WISC32M.ABASE.TWO assign
(cast(indexcol(\TESTSYS.$BIG18A.WISC32M.ABASE.TWO)) + cast(1)))
part_key_predicates: (\TESTSYS.$BIG18A.WISC32M.ABASE.UNIQUE2 =
indexcol(\TESTSYS.$BIG18A.WISC32M.ABASE.UNIQUE2))
begin_key: (\TESTSYS.$BIG18A.WISC32M.ABASE.UNIQUE2 =
indexcol(\TESTSYS.$BIG18A.WISC32M.ABASE.UNIQUE2))
ESP_EXCHANGE Operator
Exchange Group
An ESP_EXCHANGE operator describes a portion of an execution plan that
redistributes the input data stream. This operator represents an interface between
ESPs, between the master executor and one or more ESPs, or between an ESP
process and a DAM process. For more information about exchange operators, see
Section 8, Parallelism.
Token Followed by ... Data Type
new_rec_expr Computation of the row to be
updated
expr(text)
begin_key Expression of the begin key
predicates
expr(text)