openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1973) Unlocked field support
Date Sun, 03 Apr 2011 06:50:05 GMT

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

Patrick Linskey commented on OPENJPA-1973:
------------------------------------------

Basic docs: annotate a persistent property with @Unlocked, and OpenJPA will not include that
field in optimistic lock computation when using any lock variant that derives from ColumnVersionStrategy.
See openjpa-persistence-jdbc/src/test/java/org/apache/openjpa/jdbc/meta/strats/EntityWithUnlockedFields.java
for an example.

> Unlocked field support
> ----------------------
>
>                 Key: OPENJPA-1973
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1973
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: docs, jdbc, jpa
>            Reporter: Patrick Linskey
>            Assignee: Patrick Linskey
>         Attachments: OPENJPA-1973.patch
>
>
> Often, it's desirable to exclude certain fields from the optimistic locking computation.
For example, if a PurchaseOrder's lastUpdatedDate field is updated every time a line item
is added, it may be acceptable to simply use the latest value instead of requiring an optimistic
lock check / collision.
> Let's add support for such fields.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message