-
Notifications
You must be signed in to change notification settings - Fork 872
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
Unique constraint not checked after server shutdown/start #1674
Comments
What version? |
On 1.6.0-SNAPSHOT. |
That is from final snapshot, duplication check works. Please reopen issue if problem still is reproduced on your side. 2013-09-20 09:28:45:743 INFO Loading configuration from input stream [OServerConfigurationLoaderXml] 2013-09-20 09:28:47:389 INFO OrientDB Server is shutting down... [OServer] 2013-09-20 09:28:48:004 INFO OrientDB Server v1.6.0-SNAPSHOT is starting up... [OServer] |
I have a unique constraint on a property of a class but I'm still able to insert new documents after a server shutdown/start.
In my test case, the second time that I call db.save(), the user is created even though the name is supposed to be unique...
Class UserTest where a Unique index is set on the name property:
The actual test case is the following:
The text was updated successfully, but these errors were encountered: