You can try to check edges presence directly, but it will never work in multithreading environment. You should relay on index for this cases.
On Tue, Mar 11, 2014 at 10:54 PM, cp2 <[email protected]> wrote: > > >>>*So every time you will have duplication exception will be thrown and > transaction will be reverted. * > >> Can checking for edges be done directly? I would like to be able to >> perform larger transactions, so depending on exceptions makes the logic >> more difficult to fix up the vertex creation logic before retrying the >> create. >> > That is, I would like to check for the edge before I start my transaction. > > in sql you can always do this > > *select from e where out=#11:1 and in=#11:0* > > but directly accessing the implementation seems suboptimal > Something like *getEdges(<from-expression>, <dest-expression>) *returns > a set > and/or > *getEdge((<from-expression>, <to-expression>)* > returns null or an edge > > in SQL this might be* select from E where <from-expression> AND > <to-expression>* > For this to be work for anything other than single vertices, the edges > would have to be *materialized* ie not *lightweight* > > being new here, this syntax may not be ideally integrated with existing > functionality, but something like this would be helpful. > > -- > > --- > 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. > -- Best regards, Andrey Lomakin. Orient Technologies the Company behind OrientDB -- --- 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.
