On 2018-03-15 11:47, Fabián Mandelbaum wrote:
I'll try to provide the details for dependency hell with 2.6 and other
frameworks/libs later, I'm a bit overloaded with other things now, sorry.
Thanks.
Nothing happens with the tree, OK, but is it eligible to be
garbage-collected or not?
I wouldn't call it "garbage" :-) But yes, it should be possible to
delete those.
Indeed, if you try to delete a referenced node you get a
ReferentialIntegrityException, which is fine. Now, I'll be fine with
writing a robot (periodically-run task) to find all such orphans and
wipe them. How can I detect those orphans SAFELY (in a way that
attempting to delete them will not throw ReferentialIntegrityException,
and will not break my content repository in any way). Is there a
ready-made utility method in the API or a query, or set of queries, I
can run to detect those orphans?
Thanks again for your help.
I'm not sure there's a way to write a query for this.
You should be able to traverse the versions storage and find the
unreferenced version histories. That said, why don't you simply collect
the paths while deleting the version-controlled nodes?
Best regards, Julian
