Granny's Programming Pearls
"inside of every large program is a small program struggling to get out"
JavaRanch.com/granny.jsp
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Bear Bibeault
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Knute Snortum
  • Junilu Lacar
  • Devaka Cooray
Saloon Keepers:
  • Ganesh Patekar
  • Tim Moores
  • Carey Brown
  • Stephan van Hulst
  • salvin francis
Bartenders:
  • Ron McLeod
  • Frits Walraven
  • Pete Letkeman

about Entity relationship locks when Pessimisitc_write is set for an entity instance  RSS feed

 
Ranch Hand
Posts: 1703
12
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,
In test 1 of Enthuware, it points out that


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 ?

 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!