Hi, if I remember well.
2013/12/27 Dante <[email protected]> > > *alter database custom useClassForEdgeLabel=false* > > If true, edges labels are modeled as subclasses of E (the top edge class). In this way you can query for example: SELECT * FROM Friend instead of: SELECT * FROM E WHERE label = "Friend" It's a matter of efficiency. I guess that if useClassForEdgeLabel = true, you can't use lightweight edges. > *alter database custom useClassForVertexLabel=false* > > The same thing as for edges. If your query always require to discriminate vertices / edges by their label, using classes for label it's a good idea. > *alter database custom useVertexFieldsForEdgeLabels=false* > > If this is true edges are lightweight, and their label is attached to the in/out field for the respective vertices. Consider docA -- friendOf --> docB: you will find a field out_friendOf in docA and a field in_friendOf in docB. In this case the isn't any document representing the edge, just those two fields. It would be nice having confirm from Luca or his team. Cheers, Riccardo -- --- 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/groups/opt_out.
