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 05:38:05 GMT

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

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

Oh, and this is implemented against trunk (2.2.0?). I actually need this against 2.1.0 (or
for 2.2.0 to release soon). What's the process these days for backports etc.? Is there a backport-having
mvn repo / branch?

Also, I've got commit rights, but have been negligent in contributing recently. Shall I push
this, or just interact via JIRA patches?

> 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