Hi, > That's great news; I did not think unique constraints had been fixed.
Nope. Unique constraints can be placed by annotations/xml descriptors. But the topological sorting algorithm that imposes an order on sql statements to satisfy both database constraints and object-level operations do not consider unique constraints. So if a transaction removes x1 and inserts x2 while x1 and x2 has the same value for a unique non-primary column then OpenJPA *does not* ensure that DELETE x1 will be issued before INSERT x2. -- View this message in context: http://n2.nabble.com/sql-ordering-tp779562p782703.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
