Thanks Mike, I tried your suggestion, but it had no effect. The persist-order (as shown by logging @postPersist) is still in depth-first order of the object graph.
I'm almost certain I tried @ForeignKey before and after adding the UpdateManager property. Using @ForeignKey had the curious effect of causing the column to be omitted from the insert (and DB2 apparently validates non-nullable constraints before referential integrity constraints, and so the insert fails on null-nullable column is NULL). -- View this message in context: http://openjpa.208410.n2.nabble.com/Order-of-insert-tp5704835p5707205.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
