Hi Hung Tran,

a possible approach would be to create an index SB -TREE EntityInfo.State 
NOTUNIQUE instead of a NOTUNIQUE_HASH_INDEX to avoid the sorting in the use 
of this index . This is because the indexes SB - TREE retain sorting , 
making it unnecessary sorting operations (like ORDER BY).

Hope it helps

-- 

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