-
Notifications
You must be signed in to change notification settings - Fork 871
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cannot change edge's in/out with @rid #9071
Comments
Hi @tolgaulas Thank you for reporting, I'll check it ASAP and let you know Thanks Luigi |
Hi @tolgaulas I just tried it with the following
And it seems to work fine. Thanks Luigi |
Hi, can you run this and see select from V at the end in a blank DB please?
|
I made it .toJson() and here is the result: Mind the #60:2.
|
And I guess, here may be problem:
#60.2 should not be appeared here.
|
Hi @tolgaulas Thank you very much. Thanks Luigi |
Not necesarely in batch, here is the before state, the select op and the after state. See #62:2
|
Hi @tolgaulas I just tried your script and I see a consistent graph at the end... This is the expected behaviour, the update of Thanks Luigi |
Hi @luigidellaquila , the screenshot is correct. The empty array in #58:0's in_one_two may cause problem with "is null" filter operations, doesn't it? If we set the new |
Hi @tolgaulas The empty array won't cause any problems, in general I'd suggest to use graph operators to check if edges exist, (eg. Thanks Luigi |
Thank you very much.
Tolga Ulas
+90 533 7464908, skypeid:tolgaulas
…On Thu, Nov 28, 2019 at 2:59 PM luigidellaquila ***@***.***> wrote:
Hi @tolgaulas <https://github.com/tolgaulas>
The empty array won't cause any problems, in general I'd suggest to use
graph operators to check if edges exist, (eg. out().size() > 0) and avoid
null checks on out_* and in_* attributes
Thanks
Luigi
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9071?email_source=notifications&email_token=AAK5MQS4UFCL3PBLTMH57L3QV6XCXA5CNFSM4JQAOLXKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFMMRTY#issuecomment-559466703>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAK5MQVVP4M6SOM74WELA3DQV6XCXANCNFSM4JQAOLXA>
.
|
OrientDB Version: 3.0.25
Java Version:
OS: Win 2019
Expected behavior
--before--
v1(#1:1) -out- edge1(#2:1) -in->v2(#1:2)
v1(#1:1) -out- edge2(#2:2) -in->v3(#1:3)
--op--
update edge #2:2 in=#1:2
--result--
v1(#1:1) -out- edge1(#2:1) -in->v2(#1:2)
v1(#1:1) -out- edge2(#2:2) -in->v2(#1:2)
Actual behavior
v1(#1:1) -out- edge1(#2:1) -in->v2(#1:2)
v1(#1:1) -out- edge2(#2:2) -in->v3(#1:3)
--op--
update edge #2:2 in=#1:2
--result--
v1(#1:1).out =[]
v2(#1:2).in =[#2:1,#2:2]
v3(#1:3).in=[]
edge2.in = #1:1
edge2.out = #1:2
Steps to reproduce
When I change an edge’s in/out property with @Rid (ie. update edge theEdge in=#12:12) the "out"ing vertex is loosing the link. And the simple traversing queries stop working.
Instead, one have to use the select notation instead of direct rid (i.e update edge theEdge in=(select from #12:12).
Yet, the "out"ing vertex still keeps an empty out_theEdge=[ ], which looks like having no impact in the internal engine, yet it’s disturbing.
The text was updated successfully, but these errors were encountered: