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

Orient 3.0 - Unique index on edge is not working as expected #7453

Closed
careerscale opened this issue May 26, 2017 · 4 comments
Closed

Orient 3.0 - Unique index on edge is not working as expected #7453

careerscale opened this issue May 26, 2017 · 4 comments
Assignees
Labels

Comments

@careerscale
Copy link

OrientDB Version: 3.0

Java Version: 1.8

OS: Win 7

Expected behavior

The constraint like this one below
create property LIVES_IN.out LINK User;
create property LIVES_IN.in LINK Address;
create index UNIQUE_LIVES_IN on LIVES_IN(out,in) unique;

should ensure something like this

Luca LIVES_IN London
Luca LIVES_IN Rome
Luigi LIVES_IN Rome

work fine, and when we get same relation twice

say another
Luca LIVES_IN London

it should break

Actual behavior

it breaks right at 3rd line
Luigi LIVES_IN Rome

Steps to reproduce

https://github.com/careerscale/orientdb-demo/blob/master/orientdb-java-sample/src/test/java/com/orientdb/samples/test/OrientDBInvalidTxCounterTest.java
and check createUser_gremlin() method, run it.

@careerscale
Copy link
Author

any update on this one?

@tglman tglman closed this as completed Jun 5, 2017
@tglman
Copy link
Member

tglman commented Jun 5, 2017

hi @careerscale,

I just pushed this commit: 5af5f02 that fix this issue, the today snapshot should have this problem fixed.

Closing this.

Regards

@careerscale
Copy link
Author

@tglman
is this issue
#7470 because of the 7453?

@wolf4ood
Copy link
Member

wolf4ood commented Jun 6, 2017

Hi @careerscale

nope it's not related. I'm working on a fix.

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

4 participants