The order of SQL statements issued for update is determined by org.apache.openjpa.jdbc.kernel.UpdateManager interface. At configuration-level, the property is specified by the value of 'openjpa.jdbc.UpdateManager' key. Two possible values are 'constraint' and 'operation-order' -- the former being the default.
'constraint' UpdateManager evaluates the foreign key relations to reorder the statements (but not the unique constraints on non-primary key columns). 'operation-order' UpdateManager follows the order in which the object-level operations were issued. Miroslav Nachev wrote: > > How can I control the real database statements order? For example when I > am > in some Pre Callback method I would like to be sure that some database > statement call will be invoked before main statement. > Another case is when I have custom Sequence Generator and would like to > persist the Id for some object which will be stored and the main object > will > require Id object to exists in the database. > Any ideas? > > Miro. > > -- View this message in context: http://www.nabble.com/How-to-control-manage-database-statements-order-tp14579475p14580883.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
