Conversation
Notices
-
For the last 3 (!) days (including today) I tried to fix the problem that while the #JPA is merging (similar to UPDATE #SQL statement) entities, some tables got filled with new rows (search for "eclipselink insert instead update") which leaves orphaned rows behind. I could enable orphanRemoval=true but that only adds another performance penalty. So I decided to switch to #Hibernate instead of remaining with #EclipseLink. cc !java
