Changes

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 index structures[[Indexes#Value Indexes|value indexes]]. If As long as no updates have been are performed on a database, the ''PREpre'' and ''IDid'' values are identical. This also applies The values will remain to be identical if new nodes are attached 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:

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 a specific the original node. By default, ''IDid'' lookups can be are expensive; the [[Options#UPDINDEX. If {{Option|UPDINDEX]] option can be }} is turned on to build , an additional index and will be maintained to speed up the process.