May be I am not understanding the issue you raise. SQL inserts/updates are issued at commit()/flush() time only (or as implicit side-effect of query execution under some circumstances).
How about calling flush() from the callback method? That will allow runtime control of *when* SQL statements are executed against the database -- but how the statements will be ordered will remain, I think, in the realm of statically-configured UpdateManager. -- View this message in context: http://www.nabble.com/How-to-control-manage-database-statements-order-tp14579475p14592067.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
