-
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
After combination of setEdge and select by rid index is broken down #8224
Milestone
Comments
Looks like tx visibility issue |
tglman
added a commit
that referenced
this issue
Apr 19, 2018
Hi @sreznick, Thank you for reporting this I could reproduce the problem and fix it. Regards |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
OrientDB Version: 3.0.0_RC2
Java Version: 9.0.4
OS: ubuntu docker image under Windows 10
Expected behavior
select by value that is exactly equal with just added should return corresponding vertex
Actual behavior
select by value using eqiuals operation does not find expected vertex. select using 'like' comparision finds it. And comenting out some seemingly irrelevant code lines changes behavior. Details are in comment lines of attached source.
Steps to reproduce
Select2.java.txt
The text was updated successfully, but these errors were encountered: