Thanks for the reply. i just saw it after my following reply to Pinaki. I do in fact have <property name="openjpa.jdbc.SchemaFactory" value="native(ForeignKeys=true)"/>
and i did add <property name="openjpa.jdbc.UpdateManager" value="batching-constraint"/> but it did not change the result. As I said in the other reply I'm definitely seeing an ordering happening from the 'leafs' of the graph to the 'root', so it does look to me like a entity duplication issue as opposed to an ordering issue. -- View this message in context: http://openjpa.208410.n2.nabble.com/Delete-OptimisticLock-exception-when-entity-appears-2x-in-cascade-graph-tp6882907p6891354.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
