Hi syshex, Adding vertices and edges are 2 independent API calls.
It's an event window where vertices and edges information come in from external sources, the vertices/edges can already be either committed data or to be added newly. So caching all the vertices/edges objects and passing it along all the API methods which need access to them is not the solution I am looking for. regards, sathwik On Friday, 20 March 2015 18:16:24 UTC+5:30, syshex wrote: > > Hi, when you create both vertex1 and vertex2, why don't you keep a > reference to those and use those references to add the edge? > > > On Friday, March 20, 2015 at 12:29:18 PM UTC, Sathwik B P wrote: >> >> Hi Guys, >> >> OrientDB 2.0.2 >> >> Transaction is started, 2 vertices are added. In order to create an edge >> between the 2 newly added vertices we query for the vertex again from the >> graph. It turns out to return a null object. >> >> *Are objects added in the same transaction not visible for re-reads?* >> >> Here is the scenario. >> >> Transaction begin >> >> Add vertex1 >> Add vertex2 >> >> Add edge >> * Get vertex1 -> this is null object* >> >> Transaction commit >> >> regards, >> sathwik >> > -- --- 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.
