XQuery Update

From BaseX Documentation
Jump to navigation Jump to search

With the release of version 6.0, BaseX offers a complete implementation of the XQuery Update Facility (XQUF).


With XQuery Update you can modify the content of an xml database with a huge variety of functions. There are some hints you should know:

  1. A XQuery Update query can never return a result. So you can't combine reading queries and updating queries into one query, even if they are separated with a comma.
    Incorrect Query:
    for $i in 1 to 10 return $i, insert nodes <test/> into root()
  2. Updates of a XQuery Update query are not visible until the whole query is finished. So values generated by subqueries are not accessible in the other parts of the query. This is because XQuery Update uses a so-called pending update list in the processing model and executes all updates at the end of the query.
  3. The order of XQuery Update functions in a query is irrelevant. There is a specification which controls the execution order of the update functions.
    insert nodes <a/> into root(), delete nodes //a
    Result: Node <a/> is still in the database, because the delete function didn't find the nodes inserted by the insert function.

XQUF Concepts

There are a few specialties around XQuery Update that you should know about. In addition to the simple expression, the XQUF adds the updating expression as a new type of expression. An updating expression is able to change the state of a database node, whereas a simple expression cannot perform any permanent changes.

Pending Update List
The most important thing to keep in mind when using XQuery Update is the Pending Update List (PUL). In contrast to other programming languages, XQUF statements are not executed immediately, but are first collected within a set-like structure, the PUL. At the end of a query, all update primitives on this list are applied after being checked for compatibility. If a conflict exists, an error message is returned and all accessed databases remain untouched (atomicity). For the user this means updates are only visible after the end of a snapshot.
Returning Results
It is not possible to mix different types of expressions in a query result. The outermost expression of a query must either be a collection of updating or non-updating expressions. Spoken clearly, you cannot perform any updating queries and return a result at the same time.

common error: copy/fragment of dbnode-> change for result. better use transform

Function Declaration
To use updating expressions within a function, the 'updating' flag has to be added to the function declaration. A correct declaration of a function that contains updating expressions (or a function that calls updating functions) looks like this: declare updating function { ... }

New Updating Expressions

There are five new expressions to modify data. While insert, delete, rename and replace basically explain themselves, the transform expression is different. Modified nodes are copied in advance and the original databases remain untouched.


An expression consists of a target node (the node we want to alter) and additional information like insertion nodes, a QName, etc. which depends on the type of expression. You can find a few examples and additional information below.






fn:put() Function

FN:put() is also part of the XQUF and enables the user to serialize XDM instances to secondary storage. It is executed at the end of a snapshot. Serialized documents therefore reflect all changes made effective during a query.

Effects on Your Documents

In BaseX, all updates are performed on database nodes. This is why update operations never affect the original input file. You can, however, use the EXPORT command or the fn:put() function to create an updated XML file. Turning on the WRITEBACK property (SET Command) directly propagates changes of your database to the original input file. Make sure you back up your data in advance, as this approach modifies the underlying XML file.


As BaseX aims mainly for efficiency, the maintenance of indexes is left to the user. This requires the user to call the Optimize command if up-to-date index structures are necessary. Using this approach guarantees fast updates and fast access at the same time.


So far BaseX differentiates between fragments and database nodes. Updates on fragments have no effect on any existing databases and are therefore not applied at all. This includes the test for violation of any constraints. Thus it is possible to execute an update on a fragment, which would raise an error if applied on a database node.

Example 1
insert node attribute id{'1'} into <a id='0'/>
Example 2
insert node attribute id{'0'} into doc('doc.xml')//n
File 'doc.xml': <n id='1'/>
Result: [XUDY0021] Duplicate attribute "id".

Fragments & fn:put()

As a consequence, updates on a fragment are not visible in an XML file created with fn:put(). If this functionality is required, the transform expression can be applied. The copied nodes in a transform expression are internally treated like database nodes and are updatable as a result.

Example 1
let $n := <n/> 
 return (insert node <x/> into $n, put($n,'doc.xml'))
Resulting File 'doc.xml': <n/>
Example 2
 copy $nn := <n/> 
 modify insert node <x/> into $nn 
 return $nn, 'doc.xml' 
Resulting File 'doc.xml': <n> <x/> </n>