Hello,
When checking if an edge already exists before creating a new one (for an
import)
I was doing:
select in.key, out.key
from has_property
where out.key = 'a2adb112-a3a4-11e3-ace8-005056872b95' and in.key =
'a3eb10b0-a3a4-11e3-ace8-005056872b95'
This works, but it is slow, since you're not using the index to lookup the
edges.
So I rewrote it like this (as I did for a few other similar queries):
select key
from School
where key = 'a2adb112-a3a4-11e3-ace8-005056872b95'
and in( 'has_property' )[ key =
'a3eb10b0-a3a4-11e3-ace8-005056872b95' ].key is not null
This will start by using the index to find the school with key=xxx, and
then look through the edges to find if it is connected to another node with
key yyy.
Unfortunately, in this case it didn't work, and i get:
java.lang.NumberFormatException: For input string: " key = 'a3eb10b0"
(There is a string index on that 'key' property)
Similar queries were working without problems, for example:
select key
from School
where key = 'a2a691e8-a3a4-11e3-ace8-005056872b95' and in(
'provides_services_for' )[ institutionNumber= '114546' ].institutionNumber
is not null
is working as expected.
Any ideas what might be wrong?
I am using the 1.7 snapshot version from a few days ago (1st of april I
think)...
--
---
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.
