openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kevin Sutter (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OPENJPA-1973) Unlocked field support
Date Tue, 05 Apr 2011 13:24:05 GMT

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

Kevin Sutter commented on OPENJPA-1973:
---------------------------------------

Hi Patrick,
Yes, that makes more sense.  Let me rephrase...  You are just trying to identify which attributes
should be monitored (or not monitored) for the @Version field check.  You still want the @Unlocked
fields to be persisted, but don't monitor these to determine whether the @Version field should
be updated or not.  Or, would you go ahead and still update the @Version field, just don't
care about the version checking if the only fields updated were the @Unlocked fields?

Thanks,
Kevin

> 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-with-docs.patch, 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