Hi, We are currently evaluating OrientDB for research proposes. In our environment we want to store a 'commit' into the database. A 'commit' consists of multiple (about 10000) vertices and edges - each of these vertices/edges should be either created, updated or removed.
Currently we use a remote connection and the Java API to perform the necessary changes. Buy using the Java API for updating a vertex we retrieve it by the node rid and apply the changes. Similarly when we create edges between existing nodes we need to retrieve the nodes to create an edge between them. These process of retrieve and changing could be done similarly with two simple OrientDB SQL queries like: "update vertex #x:yz set ..." and "create edge xzy from ... to..." without the need to fetch the vertexes before. I've two questitions: 1.) Can anyone confirm that the Java API is actually contacting the server each time we get a vertex by it's rid (even if we have not commited the transaction yet). 2.) If yes: Is there a better way to execute the changes at server side only (just communicating once)? Thank you for your help in advance! Philipp Schindler -- --- 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.
