You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Rick Curtis (JIRA)" <ji...@apache.org> on 2010/04/08 22:22:36 UTC
[jira] Assigned: (OPENJPA-1604) Setting PessimisticLockManager
fails to append "for update clause" to the select statement
[ https://issues.apache.org/jira/browse/OPENJPA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rick Curtis reassigned OPENJPA-1604:
------------------------------------
Assignee: Rick Curtis (was: 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: Rick Curtis
> Fix For: 2.0.0, 2.1.0
>
> Attachments: OPENJPA-1604-2.0.x.patch, OPENJPA-1604-trunk.patch
>
>
> 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.