I have written an 'after record create' server side hook to automatically create a secondary pair of vertex and connecting pair of edges every time a particular record type is created. If the secondary vertex already exist I only link to them.
To test, I create several hundred entries and populate via a single thread client app (in a for loop!) It works fine as long as the secondary vertex are all new but as soon as I am creating, accessing and linking both new and existing vertex I get a lot of negative rids or misaligned versioning. I don't really know the right way to go about this task, are transactions the right approach? It is hurting my brain!! -- --- 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.
