SCAN |
(+C1,-C2)
(C1[(1U)+/A/B/C])
(C1[(1U)+declare namespace aaa
="http://www.w3.org/XML/1998/namespace";/A/B/aaa:C])
(C1[(1U)+/A/B/xml:C])
WITHIN(C1,..)[SCAN TYPE]
CONTAINS (C1,..)[INDEX SCAN TYPE]
SEARCHFEATUREDATA (C1,..)[FULL SCAN TYPE]
SCAN |
(+C1,-C2)
(C1[(1U)+/A/B/C])
(C1[(1U)+declare namespace aaa
="http://www.w3.org/XML/1998/namespace";/A/B/aaa:C])
(C1[(1U)+/A/B/xml:C])
WITHIN(C1,..)[SCAN TYPE]
CONTAINS (C1,..)[INDEX SCAN TYPE]
SEARCHFEATUREDATA (C1,..)[FULL SCAN TYPE]
where C1='A' work table number: 1
or C2=between 'a' and 'z' work table number: 2
: |
SCAN |
(+C1,-C2)
SCAN |
(+C1,-C2)
SCAN |
SCAN |
SCAN |
SCAN |
--- SELECT-APSL --- |
1 and 2 indicate the first candidate and second candidate, respectively, for the access path. For details about the types of access paths, see 17.5.8 Types of access paths.
For a HiRDB single server configuration, the single server creates two SQL objects for the entire SQL statement without executing SELECT-APSL for each join and retrieval processing.