openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Albert Lee <allee8...@gmail.com>
Subject Re: [jira] Updated: (OPENJPA-1604) Setting PessimisticLockManager fails to append "for update clause" to the select statement
Date Thu, 08 Apr 2010 20:33:27 GMT
Please localized the trace message.

Thanks
Albert Lee.

On Thu, Apr 8, 2010 at 2:07 PM, Rick Curtis (JIRA) <jira@apache.org> wrote:

>
>     [
> https://issues.apache.org/jira/browse/OPENJPA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel]
>
> Rick Curtis updated OPENJPA-1604:
> ---------------------------------
>
>     Attachment: OPENJPA-1604-2.0.x.patch
>                OPENJPA-1604-trunk.patch
>
> > 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
> >
> >         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.
>
>


-- 
Albert Lee.

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message