Thanks Patrick, that could work. The only thing I would be concerned about is the implications for querying the data, it would mean multiple instances of the Tag edge for the same tag content which would probably result in more complex and possibly less efficient queries for anything relating to unique tags. It's an interesting idea though that I will consider and it keeps the schema nice and simple. -Phil
On Monday, 16 March 2015 21:19:48 UTC+1, Patrick Hoeffel wrote: > > Phil, > > What if you made the Tag itself the Edge class, and perhaps add a couple > of properties to the edge to give it appropriate context? Then your > three-node graph above becomes a two-node graph with multiple "Tag" edges > between them? You could add the timestamp to record when the Person add the > Tag to the Resource. > > Would that work? > > Patrick > > -- --- 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.
