I thought a solution for it in the case no other better solution actually exists :
when i create a document inside the transaction the id is valid but point to a special cluster (transaction cluster) so i can associate it in other odocuments ... without exceptions when i make commit orientdb remap the associations with the right new real id :) :) Il giorno venerdì 5 giugno 2015 12:19:35 UTC+2, Cristian Lorenzetto ha scritto: > > in many cases i have a transaction and > inside this transaction i have to create a new document and then to bind > it to another document. > > when you create a new document, it has a invalid id until you make a > commit. Is there other solutions? > > > The solution acctually is : > to make a commit after document creation and in case of rollback i have to > remove document manually > but is there other better solution ? > for example if i create a nested transaction for the document creation i > can have correct it ? > -- --- 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.
