We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In OrientDB 2.2.35 this query worked fine:
MOVE VERTEX (SELECT FROM Uncompleted_Personal_Task WHERE @Rid = #105:1) TO CLASS:Completed_Task
It moved the vertex into the Completed_Task class and it kept all its edges.
In OrientDB 3.0.1 the same query moves the vertex into the Completed_Task class but all its edges disappear.
The text was updated successfully, but these errors were encountered:
Hi @castrv
I'm checking it now, I'll let you know asap
Thanks
Luigi
Sorry, something went wrong.
54b3d63
I just pushed a fix, it will be released with v 3.0.2
luigidellaquila
No branches or pull requests
OrientDB Version: 3.0.1
Java Version: openjdk version "1.8.0_171"
OS: Debian 9.4
Expected behavior
In OrientDB 2.2.35 this query worked fine:
MOVE VERTEX (SELECT FROM Uncompleted_Personal_Task WHERE @Rid = #105:1) TO CLASS:Completed_Task
It moved the vertex into the Completed_Task class and it kept all its edges.
Actual behavior
In OrientDB 3.0.1 the same query moves the vertex into the Completed_Task class but all its edges disappear.
Steps to reproduce
The text was updated successfully, but these errors were encountered: