There is just no need to define indexes on the parent class, as long as you have indexes on the same properties on the subclass. Eg. if you have a class A with two subclasses A1 and A2 and both subclasses have an index on "name", if you do a
SELECT FROM A WHERE name = 'foo' it will use the indexes on the subclasses Thanks Luigi 2016-07-28 8:48 GMT+02:00 hartmut bischoff <[email protected]>: > Thanks for the quick response. > > Unfortunately, this leads to other Questions, probably due to a lac of > skills on my side > > 1. How does this affect queries based on the superclass? > The Match-Query presented in another topic is already slow. > > 2. Do I have to define two indexes, one on the superclass (non-unique) and > in addition one on every Subclass (unique). > > 3. Can I use the same name for the indexes on the subclass-level and are > they combined if a query on the superclass is performed. in case there is > no index defined for the superclass? > > > > -- > > --- > 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.
