I now my issue is a bit complicated since I don't have any sample code to show you, but maybe it can highlight some unexpected behaviors on unique indexes?
Feel free to tell me if you have any idea of something I could try to have more informations about this issue. I already tried everything I had in mind... :( Thanks a lot!! Le jeudi 20 octobre 2016 14:41:00 UTC+2, Fabien Antoine a écrit : > > Hi, > > I'm getting a very strange and almost random "unique constraint violated" > error. > I didn't succeed to reproduce it on a small sample, but maybe you'll have > some idea of wha'ts going on. > > I'm working with ArangoDB 3.0.10 (but it also happened before this > version) on a non-clustered environment, using ArangoJS driver. > > I have a fixture manager which is in charge of clearing the database with > a `truncate` command, ensuring indexes and then inserting all fixture data > into Arango. > > This works pretty well but I'm getting random errors of "unique constraint > violated". By random I mean: > - sometimes fixtures are all loaded correctly ; > - sometimes it crashes in the middle of my fixture set, but for different > entries. > > I already checked if collections are correctly truncated, and it's the > case. > The worst thing is that there is no duplicate of the incriminated entry in > the collection. > It's just like if Arango is keeping a kind of cache of some unique > entries... > > If you have any idea of why I'm getting this kind of error, or some > solutions to try, let me know please. > > Thanks for your help and this great DB! > > -- You received this message because you are subscribed to the Google Groups "ArangoDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
