You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a create a vertex, I get a temporary ID (ends with ":-2"). I can retrieve that vertex
with the string representation of the ID only in the same transaction.
If I open a new transaction, the ID is unusable
OrientDB uses temporary rids in transactions and are resolved at commit time.
That means that if you store a termporary rids in a String you will get the temporary rid.
Thank you for your answer.
In my case, transaction encompasses the whole HTTP request process, including the build of the response.
I think that it is not a good idea to commit the transaction before each id obtained because the process could fail after that, rollback won't be possible.
When a create a vertex, I get a temporary ID (ends with ":-2"). I can retrieve that vertex
with the string representation of the ID only in the same transaction.
If I open a new transaction, the ID is unusable
I suppose replacing ":-2" by ":0" is not the solution.
How can I provide a stable ID to client (I am in a web application context) ?
The text was updated successfully, but these errors were encountered: