[OPENJPA-1604] Setting PessimisticLockManager fails to append "for update clause" to the select statement

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0
• Fix Version/s: 2.0.0
• Patch Info: Patch Available
• Assignee: Richard G. Curtis
• Reporter: Fay Wang
• Created: 30/Mar/10 20:44
• Updated: 30/Jun/10 21:00
• Resolved: 10/Apr/10 17:41

Description

I ran a testcase against openjpa 1.2, and found that the "for update" clause is appended to the SQL when

<property name="openjpa.LockManager" value="pessimistic"/>

is added to the persistence.xml without calling:

q.setLockMode(LockModeType.PESSIMISTIC_WRITE);

However, this behavior changes when running against trunk level code

Issue Links

• incorporates: OPENJPA-1714 Consider openjpa.Optimistic setting when calculating the default lock mode to apply to a named query
• is related to: OPENJPA-1629 Executing a named query with a lock mode greater than NONE throws the wrong exception

Sub-Tasks

• Add test variation to TestNamedQueryLockMode: Closed