On 25 March 2014 12:20, MrFT <[email protected]> wrote: > 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. >
It would be much faster if you can use indexes, but seems you don't have properties on them, so you could index Vertex.key and then start from any of vertices and go back: select from ( select expand( inE() ) from V where key = 'a2a3fd48-a3a4-11e3-ace8-005056872b95' ) where out.vskoNumber = '2476' > > 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. > Look at: https://github.com/orientechnologies/orientdb/wiki/Graph-Database-Tinkerpop alter database custom useLightweightEdges=false I am quite new to OrientDB, so there's still a lot to learn, and I like to > take one step at a time. > We're happy to support new users, please give us your feedback where we can improve, or better, help us to improve the documentation where is not 100% clear. Lvc@ -- --- 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.
