[ https://issues.apache.org/jira/browse/OPENJPA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Donald Woods updated OPENJPA-1604: ---------------------------------- Patch Info: [Patch Available] Affects Version/s: 2.0.0 Fix Version/s: 2.1.0 2.0.0 Assignee: Pinaki Poddar > Setting PessimisticLockManager fails to append "for update clause" to the > select statement > ------------------------------------------------------------------------------------------ > > Key: OPENJPA-1604 > URL: https://issues.apache.org/jira/browse/OPENJPA-1604 > Project: OpenJPA > Issue Type: Bug > Affects Versions: 2.0.0, 2.1.0 > Reporter: Fay Wang > Assignee: Pinaki Poddar > Fix For: 2.0.0, 2.1.0 > > > 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 -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.