hi, to resolve your question there are various way as rightly you have listed too. One of these ways, perhaps the simplest approach, might be the one shown in the picture:
<https://lh3.googleusercontent.com/-w6aI4poMuUc/VcBuEpzbCgI/AAAAAAAAAE4/QThKWSIyuDw/s1600/schema.png> It should not (I think, the only way to be sure would compare it with other solutions) be a bad idea to develop it so, because you have a field that indicates if the node is active or not and there are N edge of individual nodes linked to duplication. As DB structure should not be complex / expensive relative to the performance of the DB side. I repeat, it is one of the possible N solutions.. this is the best solution? to answer the question should develop others and then compare them. I do not know if you have been of help, I told you the way I would have done .. regards, Savio L. <https://lh3.googleusercontent.com/-w6aI4poMuUc/VcBuEpzbCgI/AAAAAAAAAE4/QThKWSIyuDw/s1600/schema.png> -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
