Hi Max,
Does it mean that optimiize now only has to create fresh statistics? Or does AUTOOPTIMIZE make the UPDINDEX pointless?
Both options can be used side by side: UPDINDEX will take care that the value index structures will be updated as part of the actual update operation. AUTOOPTIMIZE will update the remaining data structures (full-text index, database statistics). However, if you have really large databases, AUTOOPTIMIZE will most probably take too much time.
As well, I used "statistics" here because this term is used in the docs. What does it actually meean? Is it the structural indexes?
In the article on Index structures [1], I mentioned some examples for statistical data. These include minimum and maximum values of elements and attributes, the number of their occurrence, or distinct categories. Such information can explicitly be retrieved via functions like index:element-names or index:facets.
Lastly, UPDINDEX will leave the UPTODATE flag set to false after updates. What effect does this have?
This indicates that various optimizations won’t be triggered. For example, count(//item) can be extremely fast if all meta data is up-to-date. After an update operation, the database will need to be sequentially traversed to find all item elements (because the database meta data are not reliable anymore).
Hope this helps Christian