I came across a real-world example recently that seems to cry out for "normal" edges with properties (as opposed to lightweight edges): The simplified version is a list of people and the companies they have worked for. It seems to me that an edge class between person and company classes with "start date" and "end date" properties (and maybe a "reason for leaving" property) would be ideal for this. I'm still relatively new to OrientDB and graph databases in general, so I'm wondering if there is a better/preferred way to do this (or even an alternative)? I can envision a model with an "employment" vertex as well, using lightweight edges to connect people---employment---company, where the employment vertex would have the date and other properties for a given employment period. Is this "better"? Worse? Why? --Eric
-- --- 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.
