You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@openjpa.apache.org by "Albert Lee (JIRA)" <ji...@apache.org> on 2009/06/01 21:37:07 UTC

[jira] Closed: (OPENJPA-1022) Support distinct LockModeType.READ/OPTIMISTIC & WRITE/OPTIMISTIC_FORCE_INCREMENT

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

Albert Lee closed OPENJPA-1022.
-------------------------------


> Support distinct LockModeType.READ/OPTIMISTIC & WRITE/OPTIMISTIC_FORCE_INCREMENT
> --------------------------------------------------------------------------------
>
>                 Key: OPENJPA-1022
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1022
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: jdbc, jpa, kernel
>    Affects Versions: 2.0.0
>            Reporter: Albert Lee
>            Assignee: Albert Lee
>            Priority: Minor
>             Fix For: 2.0.0
>
>
> JPA 2.0 LockModeType.READ/OPTIMISTIC and WRITE/OPTIMISTIC_FORCE_INCREMENT are semantics equivalent but they are distinct enum type. Setting these lock modes enum type should return the same enum type.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.