openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pinaki Poddar (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1604) Setting PessimisticLockManager fails to append "for update clause" to the select statement
Date Fri, 09 Apr 2010 16:20:50 GMT

    [ https://issues.apache.org/jira/browse/OPENJPA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12855455#action_12855455
] 

Pinaki Poddar commented on OPENJPA-1604:
----------------------------------------

Some of the tests such as executing a NamedQuery with lock outside a transaction should raise
an error has been @AllowFailured.
Please add the reason/explanatory texts to @AllowFailure why that is done/required. 

> 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.


Mime
View raw message