... |
The fully qualified name for an XML element is: |
{code}"model"."document name".\[path to element]."element name"{code} . |
|
The fully qualified name for an attribute is: {code}"model"."document name".\[path to element]."element name".\[@]"attribute name"{code} |
Partially qualified names for elements and attributes can be used as long as the partial name is unique. |
... |
h3. Context Function |
{code:SQL}CONTEXT\(arg1, arg2){code} |
Select the context for the containing conjunct. |
... |
h3. Rowlimit Function |
{code:SQL}ROWLIMIT\(arg){code} |
Limits the rows processed for the given context. |
... |
Limits the rows processed for the given context and throws an exception if the given number of rows is exceeded. |
{code:SQL}ROWLIMITEXCEPTION\(arg){code} |
Syntax Rules: |
... |
A valid XML SELECT Command against a document model is of the form SELECT ... FROM ... WHERE ... ORDER BY ... . The use of any other SELECT command clause is not allowed.
The fully qualified name for an XML element is:
"model"."document name".[path to element]."element name"
The fully qualified name for an attribute is:
"model"."document name".[path to element]."element name".[@]"attribute name"
Partially qualified names for elements and attributes can be used as long as the partial name is unique.
Specifies the document to generate. Document names resemble other virtual groups - "model"."document name".
Syntax Rules:
The select clause determines which parts of the XML document are generated for output.
Example Syntax:
select * from model.doc
select model.doc.root.parent.element.* from model.doc
select element, element1.@attribute from model.doc
Syntax Rules:
The where clause specifies how to filter content from the generated document based upon values contained in the underlying mapping classes. Most predicates are valid in an XML SELECT Command, however combining value references from different parts of the document may not always be allowed.
Criteria is logically applied to a context which is directly related to a mapping class. Starting with the root mapping class, there is a root context that describes all of the top level repeated elements that will be in the output document. Criteria applied to the root or any other context will change the related mapping class query to apply the affects of the criteria, which can include checking values from any of the descendant mapping classes.
Example Syntax:
select element, element1.@attribute from model.doc where element1.@attribute = 1{code * {code:SQL} select element, element1.@attribute from model.doc where context\(element1, element1.@attribute) = 1
Syntax Rules:
Sibling Root Mapping Classes Implied root context user criteria against a document model with sibling root mapping classes is not generally semantically correct. It is applied as if each of the conjuncts is applied to only a single root mapping class. This behavior is the same as prior releases but may be fixed in a future release. |
XML SELECT Command functions are resemble scalar functions, but act as hints in the WHERE clause. These functions are only valid in an XML SELECT Command.
CONTEXT(arg1, arg2)
Select the context for the containing conjunct.
Syntax Rules:
ROWLIMIT(arg)
Limits the rows processed for the given context.
Syntax Rules:
Limits the rows processed for the given context and throws an exception if the given number of rows is exceeded.
ROWLIMITEXCEPTION(arg)
Syntax Rules:
The XML SELECT Command ORDER BY Clause specifies ordering for the referenced mapping class queries.
Syntax Rules: