JPA: Eclipselink not respecting em.remove()

Question

I need to delete one entity and create another: ``` @Stateless public class StatelessBean { @PersistenceUnit(unitName = "Unit001") EntityManagerFactory emf; protected void test() { EntityManager em = emf.createEntityManager(); MyObj obj1 = em.find(MyObj.class, 100); MyObj obj2 = new MyObj(); obj2.setKey("the same unique key as in obj1"); em.remove(obj1); // em.flush(); em.persist(obj2); // works fine when flush() is uncommented em.close(); } } ``` If I leave `em.flush()` commented, then I get `com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException` (new and old objects have equal key value) What could be the reason for such an abnormal behavior? Server: Glassfish 3.1.2 Eclipse Persistence Services - 2.3.2.v20111125-r10461 persistence.xml: ```

jdbc/Unit001DS

Accepted Answer

The reason could be that Eclipselink changes the order of operations during commit as stated in the Eclipselink documentation:

By default, EclipseLink does insert and update operations first, before delete operations, to ensure that referential integrity is maintained. This is the preferred approach.

You can change this behavior either by flushing (as you already found out) or by setting a special parameter for Eclipselink:

If you are forced to replace an object with unique constraints by deleting it and inserting a replacement, you may cause a constraint violation if the insert operation occurs before the delete operation. In this case, call `setShouldPerformDeletesFirst` to perform the delete operation before the insert operation.

JPA: Eclipselink not respecting em.remove()

Solution

Problem