Skip to content
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

Can't find nearly inserted record by unique field within transaction #9281

Closed
arch7tect opened this issue Jun 5, 2020 · 2 comments
Closed
Assignees
Labels

Comments

@arch7tect
Copy link

OrientDB Version: 3.1.0

Java Version: 1.8

OS: Windows 10

Expected behavior

in transaction:
--insert record in the class with unique index
--select this record by indexed field
expected: nearly inserted record is found

Actual behavior

no records found

Steps to reproduce

drop class TestClass if exists unsafe;
create class TestClass extends V;
create property TestClass.name STRING;
create index TestClass.name on TestClass(name) unique;
begin;
let b = CREATE VERTEX TestClass SET name = 'b';
let last = (select * from TestClass where name='b');
commit;
return $last.size();

This code returns 0.
If we comment out 'create index' statement, we got 1.

@andrii0lomakin
Copy link
Member

That is a known issue I am already working on it.

andrii0lomakin added a commit that referenced this issue Jun 5, 2020
@andrii0lomakin
Copy link
Member

Fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants