Changes

Jump to navigation Jump to search
12 bytes added ,  16:54, 10 April 2019
no edit summary
</pre>
The ''===PRE'' value of a node represents the order in which the XML nodes are visited by a SAX parser. It is actually not stored in the database; instead, it is implicitly given by the table position. As a result, it will change whenever a node with a smaller ''pre'' values is added to or deleted from a database.Value===
The ''pre'' value of a node represents the order in which the XML nodes are visited by a SAX parser. It is actually not stored in the database; instead, it is implicitly given by the table position. As a result, it will change whenever a node with a smaller ''pre'' values is added to or deleted from a database. ===ID Value=== Each database node has a persistent ''IDid'' vaulevalue, which remains valid after update operations, and which is referenced by the [[Indexes#Value Indexes|value indexes]]. As long as no updates are performed on a database, the ''PREpre'' and ''IDid'' values are identical. The values will remain to be identical if new nodes are exclusively added to the end of the database. If nodes are deleted or inserted somewhere else, the values will diverge, as shown in the next example:
<pre>
</pre>
The [[Database Module#db:node-pre|db:node-pre]] and [[Database Module#db:node-id|db:node-id]] functions can be called to retrieve the ''PREpre'' and ''IDid'' values of a node, and [[Database Module#db:open-pre|db:open-pre]] and [[Database Module#db:open-id|db:open-id]] can be used to go back and retrieve the original node. By default, ''IDid'' lookups are expensive. If the [[Options#UPDINDEX{{Option|UPDINDEX]] option }} is turned on, an additional index will be maintained to speed up the process.
==Block Storage==
Bureaucrats, editor, reviewer, Administrators
13,550

edits

Navigation menu