Hi Alessandro, Yes, I've read the docs multiple times and typically we use transactions in multiple parts of the application just fine. What's unique about this case is that we adding an edge in the transaction for the newly created record (vertex). This is where Orient fails on me.
As you can see from the description, we need to execute 3 commands as part of one transaction: create new document, update property of another document and create an edge from an existing document to the newly created. The first 2 are fine, but the edge creation fails with the complaint about the RID. It seems that the edge can't be created in the transaction for the temporary RID of the just created document. I need to understand if this is a limitation of Orient and is there a better way of doing this. Intuitively, I feel that if the edge creation is the last command that must be executed when transaction is committed on the server's end, it shall use temporary RID map it internally to the permanent (since at the time of the 3rd command the created document must have the permanent RID already) and be able to create an edge. Or, am I getting this completely wrong? If so, how can I add the edge as part of the same transaction when creating a document to avoid a possibility of creating a new document without the edge? On Thursday, November 17, 2016 at 2:28:29 AM UTC-8, [email protected] wrote: > > Hi, > have you seen the documentation > <http://orientdb.com/docs/2.2/Transactions.html> ? > > Best regards, > Alessandro > -- --- 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.
