SQL/MX 3.2 Query Guide (H06.25+, J06.14+)

SQL/MX Operators
HP NonStop SQL/MX Release 3.2 Query Guide—663851-002
7-8
CURSOR_DELETE Operator
routine_name ........... CAT.SCH.U300POPULATEA
routine_label .......... \DMR11.$DATA04.ZSDJG12X.WF32X300
sql_access_mode ........ MODIFIES SQL DATA
external_name .......... populateA
external_path .......... ./
external_file .......... TEST300
signature .............. (Ljava/lang/String;)V
language ............... Java
runtime_options ........ OFF
runtime_option_delimite ' '
max_result_sets ........ 0
input_values ........... cast('customer' AS CHAR(20) CHARACTER
SET ISO88591)
CURSOR_DELETE Operator
DAM Unique Group
The CURSOR_DELETE operator describes a portion of an execution plan that works
on one row only. The CURSOR_DELETE operation is performed by first retrieving
rows from the table and then deleting each row that is required. This operation differs
from SUBSET_DELETE, in which the read and delete are performed in a combined
operation.
The CURSOR_DELETE operator has no child nodes. The description field for this
operator contains the following:
Token Followed by ... Data Type
fragment_id A sequential number assigned to the fragment.
0 is always the master executor and 1 is
reserved for the EXPLAIN plan. Numbers 2 to n
will be ESP or DAM fragments.
integer
parent_frag The fragment_id for the parent of the current
fragment. The value is (none) for the master
executor.
integer
fragment_type Master, ESP, or DP2. text
olt_optimization Indicates whether an optimization for short and
simple operations is used. Its value is used or
not used.
text
olt_opt_lean Indicates for short, simple operations whether a
further optimization that reduces the physical
size of the plan is used. Its value is used or not
used.
text
iud_type Type of delete followed by table or index name. expr(text)
begin_key Expression of the begin key predicates. expr(text)
TP663851.fm Page 8 Thursday, August 2, 2012 4:47 PM