]
Steve Ebersole closed HHH-5009.
-------------------------------
Resolution: Fixed
Support NOWAIT for "SELECT ... FOR UPDATE" with JPA
interfaces
--------------------------------------------------------------
Key: HHH-5009
URL:
http://opensource.atlassian.com/projects/hibernate/browse/HHH-5009
Project: Hibernate Core
Issue Type: Improvement
Affects Versions: 3.5.0-CR-2
Environment: Oracle / Derby
Reporter: Sergey Vladimirov
Assignee: Steve Ebersole
Attachments: DerbyTestDialect.java, Entity.java, NowaitTest.java
Original Estimate: 1 day
Time Spent: 2 days, 3 hours, 46 minutes
Remaining Estimate: 0 minutes
Test case description:
- DERBY dialect extended to add /* +NOWAIT */ SQL comment to check if it's actually
used.
- if it's working, log should contain
--- "org.hibernate.SQL DEBUG select entity0_.id as id0_0_,
entity0_.value as value0_0_ from entities entity0_ where entity0_.id=? for update with rs
/* +NOWAIT */"
-- but currently it
--- "org.hibernate.SQL DEBUG select entity0_.id as id0_0_,
entity0_.value as value0_0_ from entities entity0_ where entity0_.id=? for update with
rs"
It seems LockOptions (like "javax.persistence.lock.timeout") are lost when
converting from JPA to Hibernate. The possible place of error, from my point of view, is
loadFromDatasource() (DefaultLoadEventListener:499), where persister is loaded depending
only on LockMode without paying attention to lockOptions (including timeout).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: