I am trying to introduce Orient at work but running into a challenge with 
indexes.  They can only be created on class-level properties, which means 
that linked child properties are not allowed.  For example, say I had an 
Employee class and Company class.  The Employee class could have a LINK to 
the Company class such as employedBy.  Let's say Employee has an id 
property and Company has a name property.   Currently, you can't create 
indexes that traverse links.  I would love to create an index using the 
following:  CREATE INDEX Employee.idCompanyName ON Employee (id, 
employedBy.name) NONUNIQUE 

If you try to create the index, it will fail because the employedBy.name 
property does not directly exist within Employee. In order to get around 
this, I would be forced to de-normalize and duplicate the data. That's a 
maintenance risk and hassle. Have you considered allowing indexes on linked 
child properties?

Thanks and keep up the great work :)

-- 

--- 
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.

Reply via email to