openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Patrick Linskey (JIRA)" <>
Subject [jira] [Updated] (OPENJPA-1973) Unlocked field support
Date Sun, 03 Apr 2011 05:36:05 GMT


Patrick Linskey updated OPENJPA-1973:

    Attachment: OPENJPA-1973.patch

This patch implements this feature. Caveats:

1. I didn't even think about impact on data caching
2. The tests only cover basic field types. I expect the code works for relationship fields
also, but did not test.
3. No docs
4. I didn't test / implement XML-based configuration -- @Unlocked is the only option currently.
5. I ran a few tests, and it seemed to pass, but I have not run a full test suite.

> Unlocked field support
> ----------------------
>                 Key: OPENJPA-1973
>                 URL:
>             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:

View raw message