Hi Simon, When you execute a transaction against a database with an open transaction, the transaction is committed when the last-outside transaction commits. Assure to execute these operation against a OrientGraphNoTx instance.
Are you working with plocal or remote protocol? Lvc@ On 18 August 2014 21:17, Simon L <[email protected]> wrote: > *Original:* > BEGIN > LET vert-func1 = CREATE vertex Post SET createdAt = > "2014-08-18T16:42:13.725Z", updatedAt = "2014-08-18T16:42:13.725Z", note = > "Some > note" RETURN @rid > LET edge-func1 = CREATE edge UserWrotePost FROM #5:32 TO $vert-func1 > > COMMIT RETRY 100 > RETURN $vert-func1 > > Here's the thing- when running this many times in a row, I sometimes get > negative RIDs. It's unclear why, but it's some sort of result of failure. > > How should I make the query using a pessimistic approach? (An approach > which locks the vertex) > > Also, is there anything else what could cause failure here in a high > concurrency situation? Thanks! > > -- > > --- > 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. > -- --- 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.
