|
Hi,
just detected 2 points in code in hiberante4.3 where it is stated: // note that we acquire LockMode.READ even if it was not requested This confirms the assumption that internally LockMode.READ has become the standard lockmode for hibernate 4.3 (JPA2.1) I don't know the reasons for this change, but if it's really state-of-the-art, then the question is how to avoid these unwanted lock-upgrades from NONE to READ after an entity was been fetched from 2L-Cache and later reaccessed by a collection-query?
|