Hello,

This query, that I use to check if an edge already exists before creating a 
new one, is very slow:

select in.key, out.vskoNumber from controls where out.vskoNumber = '2476' 
AND in.key = 'a2a3fd48-a3a4-11e3-ace8-005056872b95'

Could this be speeded up? If so how? By enabling indexing on these edges?
I am doing everything using OrientSQL commands, currently, so if possible 
I'd like to know how it can be done with a query.

And another thing.
I think, to get started, that I would like to disable 'lightweight' edges 
for now, because it's more intuitive if all edges work the same way. I 
could always check out later, if I need the optimization.
But how can I disable this? I found a lot of old information that doesn't 
seem to work anymore today.
Any tips are welcome.

I am quite new to OrientDB, so there's still a lot to learn, and I like to 
take one step at a time.


-- 

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