-
Notifications
You must be signed in to change notification settings - Fork 831
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
How to update a document with unique index (constraints)? #8359
Comments
Yes, you're right. This missbehaviour was introduced with ArangoDB3.4 |
Will this be updated? When? What's the proper way to handle this now (update an object with unique constraints)? |
yes, thats why I flagged it with 'bug'. The workaround should be clear from the stackoverflow issue? 3.4.4 won't contain a fix for this, its to late in the QA pipeline already. If its more convenient for your application, try to do this in a foxx-service meanwhile. |
…'t disable indexing in rocksdb #8359
#8422 will fix this in 3.4 - if you want a fixed environment now, you may try to checkout the branch |
Hi @robert-zaremba, version 3.4.5, which includes a fix for this issue, has just been released. The latest release is available in the download section. |
Closing this issue as fixed. Updating an object with unique constraints works in 3.4.5. Working Create collection:
Add unique index:
Create document entry:
Add email in the "emails" field:
Inspect collection:
|
Thanks! |
How to properly update an ArangoDB document with unique index field?
My Environment
more details
I posted the whole question and problem on StackOverflow:
https://stackoverflow.com/questions/54916765/how-to-properly-update-an-arangodb-document-with-unique-index-field
The text was updated successfully, but these errors were encountered: