Hi Mark, Thanks.
We found that EclipseLink does the same (apperently not deactivateable, but overwriteable with API/SQL, but not yet clear what that entails). I guess the other optimizations in my questions haven't come up in real world applications? Particularly that too many different update statements flood the databases statement pool causing excessive reparsing or splitting batch/bulk updates in too many blocks loosing effectiveness. Anyway we now have info for all three main JPA-Providers. Thanks again, -- View this message in context: http://openjpa.208410.n2.nabble.com/dynamic-updates-tp7589914p7589918.html Sent from the OpenJPA Developers mailing list archive at Nabble.com.
