Currently in our project we're using Path arrays as to model one-to-many
relationships. 

 

Should we be using arrays of References instead? The obvious upside for
References is that bulk update operations would not be needed should a
node that's being referenced be moved somewhere else in the hierarchy.
How about the performance downsides? Is there a 'best practice' for
modeling one-to-many relationships in a Jackrabbit repository?

 

Thanks, Aidan

Reply via email to