Tamino XQuery User Guide - Software AG Documentation

More documents

Recommendations

Info

Performing Update Operations Note: In any of these conflict cases, the update operation is rejected by Tamino. The following tables summarize the possible conflicts. The first table shows the conflicts for operations on one element node, the other two are subsets of the first table, since not all operations can be performed on any kind of node. As an example, if you use a replace operation and an insert preceding operation on the same element node, conflict 2 arises. If you try to delete and replace the same comment node in a single update operation, conflicts 1a and 2 arise. Operations on one element node delete replace rename insert insert insert insert attribute into preceding following delete 2 1a and 2 2 2 2 2 2 replace 1a and 2 2 2 2 2 2 rename 1a — — — — insert attribute 1b — — — insert into 1a — — insert preceding 1c — insert following 1c Operations on one attribute or PI node delete replace rename delete 2 1a and 2 2 replace 1a and 2 2 rename 1a Operations on one node of some other kind delete replace delete 2 replace 1a and 2 1a and 2 44 XQuery User Guide
Performing Update Operations Examples 1a Two insert into operations on the same node: update for $a in input()/patient where $a/name/surname = "Atkins" do ( insert J. into $a/name insert Prof. into $a/name ) Although the schema allows the elements middlename and title to be inserted as child elements of name, the result of the operation depends on the order of the elementary update operations. In this case you can use two successive elementary update operations as a workaround: update for $a in input()/patient where $a/name/surname = "Atkins" do insert J. into $a/name This inserts the middlename as new child element of name, in the order that is prescribed by the schema. update for $a in input()/patient where $a/name/surname = "Atkins" do insert Prof. into $a/name And this second FLWU expression then inserts the title element. Note that this could also be performed in a single operation, when the content is declared as a sequence: update for $a in input()/patient let $i:= (J.,Prof.) where $a/name/surname = "Atkins" do ( insert $i into $a/name ) 1b Provided that the patient nodes that are retained after processing the where clause do not contain a type element with the attribute brand: 1c update for $a in input()/patient where $a/name/surname = "Bloggs" do ( insert attribute brand {"Somnex"} into $a//type insert attribute brand {"Cardiovelocimil"} into $a//type ) This conflict cannot be resolved: the operation fails with the message INOXQE 6450. This query also fails, if there already existed an element $a//type with an attribute brand. This query tries to replace the book with the title "TCP/IP Illustrated" and to add the other entries for the complete three-volume set: XQuery User Guide 45
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 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 86 and 87: Advanced Usage declare namespace in
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?