Hi Phil, You can accomplish everything you want with the three node model.
With some of the more specific queries you will need to use nested select statements to filter out specific tags or persons (or even resources if you wanted). Let me know if you need further detailed help. Best regards, -Colin Orient Technologies The Company behind OrientDB On Monday, March 16, 2015 at 11:31:37 PM UTC-5, Phil wrote: > > I was planning to have only one instance of each tag; this seems more > 'normalised' to me and may make certian queries easier/more efficient e.g. > discover all the unique tags for a resource without having to group them, > or find all resourses with a particular tag. > It's not set in stone though and I'm open to suggestions. > > > On Monday, 16 March 2015 21:36:22 UTC+1, Colin wrote: >> >> Hi Phil, >> >> Another quick question and then I'll respond to your last post based on >> your answer. Will there be a single instance of each tag (say "Family >> Photo") that multiple Person instances and Resources will use, or will >> there be multiple tag instances with the same name and properties just >> linked to different Persons and Resources? >> >> -Colin >> >> Orient Technologies >> >> The Company behind OrientDB >> > -- --- 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.
