Hi Scott, the answer is yes, when using Graph API your elements have to be instances of V and E. If you work with may graph models, you have to create you own sub-classes and sub-hierarchies under V and E and then query your own classes. OrientDB v. 2.1 also supports multiple inheritance (a class that extends two or more superclasses directly), so you graph models can someway mix. You can make V and E abstract if you want, that will just be an additional constraint.
Thanks Luigi 2015-06-15 13:18 GMT+02:00 scott molinari <[email protected]>: > Hi, > > Luigi helped me out greatly with my first question > <https://groups.google.com/forum/#!topic/orient-database/IDCYXieI6bY> on > basic concepts. Now I have another. > > When creating classes, do I always have to extend from the V or E classes > to make use of the graph API? > > If the answer is yes, then how can I create different graph models in one > database, which don't actually intersect with each other? Do I still always > create the parent nodes for each graph model extending from V and E, but > never query at the E and V superclass level? Can I make V and E abstract, > so this can be enforced? > > Scott > > -- > > --- > 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. > -- --- 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.
