An object or a child node of an object is versioned consistently exactly:
if "consistent versioning" is set for the object header and the header is going to be versioned. (Variant 1)
if "consistent versioning" is set for the object header and the header is released and the child has any versioning type and the child is going to be versioned. (Variant 1)
if "consistent versioning" is set for the object header and the child, and the header is not released and the child is going to be versioned. (Variant 2)
The following table illustrates the three possible cases.
Versioning type Header | Status header | Versioning type child | Status child | What is versioned | Variant |
|---|---|---|---|---|---|
"consistent versioning" | Released or release not available | irrelevant | irrelevant | Header | 1 |
"consistent versioning" | Released or release not available | irrelevant | Released or release not available | Child | 1 |
"consistent versioning" | Not released | "consistent versioning" | Released or release not available | Child | 2 |
This means that when versioning a child node, with "consistent versioning", no consistent versioning is performed unless the head has also set "consistent versioning". Instead, in this case, the child node is versioned in the same way as a child node with "versioning as copy, consistent scope".
If the child is versioned, the header has the versioning type "consistent versioning" and is not released, and the child has the versioning type "weak versioning", "versioning as a copy" or "versioning as a copy, consistent scope", no consistent versioning is performed.
If a node is versioned consistently, at most one version of this node can exist in the object. This means that a child node cannot be versioned consistently if the object has never been versioned. Therefore, the entire object must be versioned first.
There are two variants of "consistent versioning", which are explained in the following text.
In Variant 1, the entire object is versioned.
In Variant 2, only one node or part of the object is versioned.
Further information
Subsequently, the relocation of nodes is explained step by step within Consistent Versioning - Move Nodes (H)
A complex application example with a large object will be shown afterward. Consistent Versioning - Complex Example (H)