Hi Andrey,
Thank you! i missed the inE() / outE() properties. That's what I need.
However, I found something strange:
select from [#]
Shows me let's say 10 in_MyEdge items. It should be a link between an [A]
and an [E] vertex class.
To check which these are:
select expand(inE('MyEdge')) from [#A]
and it shows me MyEdge items which has no [#E] items neither in OUT() nor
in IN() fields. Completely different.
Let's say I haven [A] = #11:0] and [E] = #30:0 and edge between these 2
items: [MyEdge] = #40:0
The upper query lists MyEdges where in = #10:10 and out = #30:5 or any
mixture. Unexpected.
No clue why. What can be the reason?
During the piloting I used delete from MyEdge very frequently. I hope this
call removes the references from both [A] and [E] items.
Also experienced that I have to turn off both cache to speed up the UPDATE
commands.
Also found that the running a loop in javascript on a single machine caused
commit issue: version conflicts.
In the a same loop the MyEdge was updated many times I think, but I commit
every single update/insert operation. It seems turning off the profile in
config file solved this issue. Is there any relation between versioning
issue and profiler?
Thank you!
L.
--
---
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.
