When an entity instance is locked using pessimistic locking, the persistence provider must lock the database row(s) that correspond to the non-collection-valued
persistence state of the instance...... Entity relationships for which the locked entity contains the foreign key will also be locked, but not the state of the referenced entities....
I tried the example in ToyAppForJPA,
Suppose, I have CustOrder id =1, Address_ID = 1.
And also I have Address id=1, zipcode = 11111 and Address id =2, zipcode = 22222.
I expect there will be an exception thrown when I attempt to change CustOrder id 1's address from 1 to 2 because the spec says the entity relationship is locked as the lock mode is set as PESSIMISTIC_WRITE.
I don't know why I can successfully change the address for CustOrder 1 ?
All of the world's problems can be solved in a garden - Geoff Lawton. Tiny ad:
RavenDB is an Open Source NoSQL Database that’s fully transactional (ACID) across your database