Hi Scott, yes, exactly, you can define your own class hierarchies in OrientDB. There is no need for a common superclass (like Object in Java), so two classes can not have a common superclass at all. V and E are just two conventional classes used for Graph representation
Luigi 2015-06-15 8:52 GMT+02:00 scott molinari <[email protected]>: > Thanks Luigi. I understand better now. Maybe your great explanation above > could be an addition to the cluster internals, to explain how OrientDB goes > beyond an RDBMS table?;-) > > To me, the most smack in the face comment you made was "but take into > consideration that you can use document classes that do not extend E or V". > I went "Doh!", when I read that.:-) And I would suppose any subclassing of > a parent document class would also mean the parent class "gets" all the > documents of the children too, being it is their parent/ superclass, > similar to E and V? > > 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.
