Tamino XQuery User Guide - Software AG Documentation

More documents

Recommendations

Info

Advanced Usage declare namespace ino="http://namespaces.softwareag.com/tamino/response2" root( for $a in collection("ino:source")/ino:module where $a/@ino:targetNamespace="http://www.examples.com/tree" return $a ) The query functions defined in an XQuery module may also be used for defining a computed index. For details on computed indexes please refer to Performance Guide > Advanced Indexes. The XQuery Tool delivered with Tamino provides convenient support for maintaining XQuery modules. Serializing Query Results When Tamino executes a query, it handles the query in terms of its data model: an XML document is treated as a tree with a document root and different types of nodes. The query result is then serialized and wrapped into a Tamino response document. You can determine the serialization by using a Tamino query pragma, or XQuery processing instruction, which always has the form {?piname?}. Like a regular XML processing instruction, it can have additional information. This section discusses the available serializations: ■ Suppressing the Response Wrapper ■ Setting the MIME Media Type ■ Defining a Custom Output Handler Suppressing the Response Wrapper Normally, when Tamino executes a query, it returns the result using a response wrapper. This is the result of the very first query in this manual: 80 XQuery User Guide
Advanced Usage You can, however, suppress the response wrapper so that you get the bare result by using the serialization pragma and choosing the method "xml": {?serialization method="xml"?} This section contains { 3 + 6 } examples. The output is then much shorter and is restricted to the query result as such: This section contains 9 examples. Setting the MIME Media Type Using {?serialization method="xml"?} always implies that "text/xml" is used as media type for the response document. You can change this by adding media-type. The following query returns a literal SVG document which has the media type "image/svg+xml": {?serialization method="xml" media-type="image/svg+xml"?} This delivers the SVG document with the appropriate MIME media type which is then set in the HTTP response header contentType. It also means that the normal response wrapper is not used. XQuery User Guide 81
Page 1 and 2:
Tamino XQuery User Guide Version 9.
Page 3 and 4:
Table of Contents Preface .........
Page 5:
Preface This document describes how
Page 9 and 10:
1 Sample bib This doctype describes
Page 11 and 12:
2 Sample reviews This doctype descr
Page 13 and 14:
3 Query Examples ■ Using Construc
Page 15 and 16:
Query Examples This section contain
Page 17 and 18:
Query Examples Explanation Again, a
Page 19 and 20:
Query Examples Explanation Building
Page 21 and 22:
Query Examples Explanation A join i
Page 23 and 24:
Query Examples Deleting Nodes The f
Page 25:
Query Examples Explanation For the
Page 29 and 30:
4 The Nuts and Bolts of XQuery ■
Page 31 and 32:
The Nuts and Bolts of XQuery (1, 2,
Page 33 and 34:
The Nuts and Bolts of XQuery Path E
Page 35 and 36: The Nuts and Bolts of XQuery NodeTe
Page 37: The Nuts and Bolts of XQuery Since
Page 40 and 41: FLWOR Expressions Currently, there
Page 42 and 43: FLWOR Expressions The order by and
Page 44 and 45: Performing Update Operations In Tam
Page 46 and 47: Performing Update Operations Renami
Page 48 and 49: Performing Update Operations Schema
Page 50 and 51: Performing Update Operations Note:
Page 52 and 53: Performing Update Operations update
Page 55 and 56: 7 Calling XQuery through a Web Serv
Page 57 and 58: Calling XQuery through a Web Servic
Page 67 and 68: 8 CRUD Usage of a Tamino Doctype as
Page 69 and 70: CRUD Usage of a Tamino Doctype as a
Page 79: CRUD Usage of a Tamino Doctype as a
Page 82 and 83: Advanced Usage This chapter covers
Page 84 and 85: Advanced Usage declare function loc
Page 88 and 89: Advanced Usage Defining a Custom Ou
Page 91 and 92: 10 Text Retrieval ■ Simple Text S
Page 93 and 94: Text Retrieval for $a in input()/pa
Page 95 and 96: Text Retrieval for $a in input()/re
Page 97 and 98: Text Retrieval Data on the Web 34.
Page 99 and 100: Text Retrieval In Tamino, you can u
Page 101 and 102: Text Retrieval ■ Location The att
Page 103 and 104: Text Retrieval perp whelp carnivore
Page 105 and 106: Text Retrieval In the context of pa
Page 107 and 108: Text Retrieval 1. Contents Translat
Page 109 and 110: Text Retrieval path separator is no
Page 111 and 112: III Related Information 105
Page 113 and 114: 11 Related Information ■ Internal
Page 115 and 116: Related Information ■ XQuery 1.0
Page 117 and 118: Index A atomization, 30 C character
show all

Tamino XQuery User Guide - Software AG Documentation

Create successful ePaper yourself

Delete template?

Save as template?