Hi Jonathan, That is because you use lightweight edges when records, are not created only links not records are created. If you wish to put unique constraints on records you need to follow this instructions -
1. set lighweight edges to false - alter database custom useLightweightEdges=false 2. apply unique index. On Wed, Mar 26, 2014 at 4:15 AM, Jonathan Rosen <[email protected]> wrote: > I put unique indexes in place for specific edge types, so that there could > only be one kind of each index. However, it appears that for some reason, > the edge sets for a specific set of vertices have been duplicated, which > violates the rules of the indexes. > > If I try to create another duplicate edge against one of the edges in this > set, the database prevents me from doing so. Therefore, it appears that the > database itself created these edge sets, perhaps in response to some > restore procedure? > > However, this obviously has created issues for me where the code only > expects one set of outgoing edges for certain vertices, and instead > encounters 2. > > Do you have any ideas why this is happening, and how to fix it? > > I think my biggest remaining complaint with Orientdb is that there seem to > be a lot of "gremlins" that arise for non-obvious reasons. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" 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. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- You received this message because you are subscribed to the Google Groups "OrientDB" 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.
