Tamino XQuery User Guide - Software AG Documentation

Advanced Usage
Defining a Custom Output Handler
You can define your own method of delivering the response document by using a server extension
(SXS) as output handler. This output handler will then act in place of the internal Tamino XQuery
processor. In general you use:
{?serialization method=""
parameter=""?}
For example, this allows using the XSLT server extension to transform query results on-the-fly:
{?serialization method="XSLT.transform"
parameter="stylesheets" parameter="stylesheets/patientRecords.xsl"?}
{ for $a in collection('Hospital')/patient
return { $a/name, $a/sex, $a/born, $a/address }
}
The method attribute identifies the output handler. The two parameters specify the XSL stylesheet
to be used and the query. Tamino then passes the query result, the list of patients, to this output
handler which transforms it using the stylesheet patientRecords.xsl.
Please note that you can also use media-type in the serialization pragma for an output handler.
Collations
For certain operations on strings such as comparison or sort operations collations are used. They
inherently determine the result of a comparison to accommodate for special regional purposes or
linguistic needs. If a collation is not defined, Tamino uses Unicode codepoints for performing
these operations. There are two ways to use collations: In the schema you can add collation information
per element by using tsd:collation. In addition, you can assign a default collation in the
query prolog such as:
declare default collation "collation?language=fr"
The string literal is the collation URI which is interpreted as relative URL with the base URI http://www.softwareag.com/tamino.
In this example, the collation defined for the French language is
used.
You can use the Tamino-specific XQuery function tf:getCollation to deploy collations as in the
following query:
82
XQuery User Guide