By design -- yes, I get that now. Maybe that should be documented because I expected inheritance to work like inheritance and didn't expect *Indexes to be 'static' among derived classes*.
Last question on this topic: ABSTRACT changes nothing here? RE: weird things with data. I can repro but a small subset of the load takes an hour. I can give you access to a box where it can be tested. But the problem goes away if each class has it's own index so I suspect that the same value appeared in multiple tables and it just combined things. If I see anything else then I will be sure to point it out. On Tuesday, August 25, 2015 at 1:13:18 PM UTC+3, Luigi Dell'Aquila wrote: > > Hi, > > by design, unique indexes on base class are shared with subclasses, if you > need a different behavior you have to manually define indexes on the > subclasses. > > About the first problem, it would help a lot if you could provide a test > case to reproduce the issue > > Thanks > > Luigi > > > -- --- 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.
