Node properties and aspects are tightly linked to nodes i.e. any update to nodes or properties is always accompanied by a version increment on the node.
Therefore we can, when deleting a node, cascade-delete the aspects and properties.
The FK constraint on the 'node_id' columns needs to get ON DELETE CASCADE and then a thorough check needs to be done on the different databases. Following this, the SQL upgrade scripts will be fairly simple: drop and recreate the FK constraint.
This will alleviate some of the changes to deleteNodesByCommitTime required for
ALF-16029. It needs to be investigated thoroughly