Hi, By far the easiest solution is to use the default COPY semantics and have the child nodes be a part of the version history of the parent.
Jukka Zitting 19.6.2012 8.38 "Lukas Kahwe Smith" <[email protected]> kirjoitti: > Hi, > > What is the recommended design pattern to version a node with all of its > children to make it easy to restore the state later on? > For example a "page" might consist of various child nodes. > > Do I version every child node separately and then tag them all with a > common name? > > regards, > Lukas Kahwe Smith > [email protected] > > > >
