openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeremy Bauer (JIRA)" <j...@apache.org>
Subject [jira] Updated: (OPENJPA-1604) Setting PessimisticLockManager fails to append "for update clause" to the select statement
Date Mon, 26 Apr 2010 19:54:33 GMT

     [ https://issues.apache.org/jira/browse/OPENJPA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jeremy Bauer updated OPENJPA-1604:
----------------------------------

    Attachment: OPENJPA-1604_optimistic_fix_2.0.x.patch

Attaching a patch for 2.0.x which takes into account the Optimistic setting when calculating
the default lock mode to apply to a named query.  This must occur in order to maintain 1.x
behavior.

> 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
>            Reporter: Fay Wang
>            Assignee: Rick Curtis
>             Fix For: 2.0.0
>
>         Attachments: OPENJPA-1604-2.0.x.patch, OPENJPA-1604-trunk.patch, OPENJPA-1604_optimistic_fix_2.0.x.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.


Mime
View raw message