bueraucrat, Bureaucrats, editor, reviewer, Administrators
907
edits
Changes
Jump to navigation
Jump to search
no edit summary
#: Result: Node <a/> is still in the database, because the delete function didn't find the nodes inserted by the insert function.
==New Expressions==<p>The XQUF offers 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. </p> ===fn:put() Function=== ==Effects on Your Documents===
<p>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 [[Commands#Export|Export]] command or the fn:put() function to create an updated XML file.</p>
===Indexes===
<p>As BaseX aims mainly for efficiency, the maintenance of indexes is left to the user.
This requires the user to call the [[Commands#Optimize|Optimize]]
command if up-to-date index structures are
necessary. Using this approach guarantees fast updates and fast access at the same time.</p>
==New Expressions==
<p>The XQUF offers 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. </p>
===fn:put() Function===
==Fragments==
: Result: <code>[XUDY0021] Duplicate attribute "id".</code>
===fn:put() and & Fragments===
<p>As a consequence, updates on a fragment are not visible in an XML file created with
<code>fn:put()</code>. If this functionality is required, the transform expression can be applied.
