[
https://issues.apache.org/jira/browse/OPENJPA-1973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13015417#comment-13015417
]
Michael Dick commented on OPENJPA-1973:
---------------------------------------
Hi Patrick,
Nice to hear from you again.
Right now this isn't something I'd take in the 2.1.0 branch - adding a feature
after shipping the release isn't something I'd do lightly.
2.2.0 is fair game though, but there's been no discussion about having a
release. Before we include this in a release we'd need to at least go through
the full test suite, look into the impact on the datacache, and see how /
whether this will impact OPENJPA-1971.
As far as committing goes - so long as the test bucket passes on Derby, you can
go ahead and commit. It'd be nice with a new feature if you could run on one or
more of the other databases though.
> 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
