Forewarning, my questions might be a bit elementary, I'm new to orientdb. So the cons with embedded would be that the relationship would only exist in the owner and would be lost if the owner is deleted resulting in ownerless objects and the owner objects would be larger? The Pro would be more easier cleanup on deletions and possibly faster data retrieval?
As for the linkset(list)(map). I maybe missing an understanding. Why would you want to store a collection verses just creating additional Links. Performance gain? Am I missing a limitation of a Link that these types allow? On Wed, Apr 8, 2015 at 11:40 PM, Colin <[email protected]> wrote: > A Link points to a single record (Document or Vertex). > > A LinkSet is a collection set of other records. Likewise, a LinkList is a > collection list of records and a LinkMap is a collection map of records. > > There are also embedded versions of these where each record is actually > embedded within the owner and no record id is created for the embedded > record(s). > > -Colin > > > On Wednesday, April 8, 2015 at 9:27:18 PM UTC-5, JTCA wrote: >> >> What are the use cases for LinkSet, LinkList, and LinkMap and how are >> they better/worse than a Link? >> > -- > > --- > You received this message because you are subscribed to a topic in the > Google Groups "OrientDB" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/orient-database/3ztJQMX-cOs/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- 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.
