Hi, just for a test I patched the class OVertexTransformer to ignore ORecordDuplicatedExceptions. But then I found that when the OAbstractTransformer was about to log the missing of the document, I got the same exception again. The reason is that the toString() method of the OVertex implicitly calls a save, which then throws the exception. See the stack trace below. But, perhaps even more importantly, I was wondering whether I you wouldn't expect the toString() method to have no side-effects? This could also become a performance issue in the end. I'm not in the details, of course. But from a high-level point of view, I think it would be better to not even try to do any data modifications within a toString() method. Ciao Gregor
-- --- 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.
