[
https://issues.apache.org/jira/browse/OPENJPA-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12845903#action_12845903
]
Pinaki Poddar commented on OPENJPA-1545:
----------------------------------------
Revision 918634 has added new version field to persistent entities for detach
tests.
What are the assumptions made in the new detach technique that required these
entities be added with a version field? If an entity does not have a version
field how will be its impact?
> Add new Detach processing
> -------------------------
>
> Key: OPENJPA-1545
> URL: https://issues.apache.org/jira/browse/OPENJPA-1545
> Project: OpenJPA
> Issue Type: Improvement
> Components: performance
> Affects Versions: 2.0.0-beta2
> Reporter: Rick Curtis
> Assignee: Rick Curtis
> Fix For: 2.0.0
>
> Attachments: OPENJPA-1545.patch
>
>
> There have been a number of mailing list posts where the net of the post is
> that someone doesn't want OpenJPA to detach their Entities because after the
> commit happens, then are all going to be gc'd. All of the detach processing
> ends up being a waste. I also observed this same behavior when running some
> performance tests.
> With this JIRA I'm going to add a new openjpa.DetachState configuration
> option which will enable a new, super fast, minimalistic detach approach.
> This change is targeted at detach processing that happens due to an
> AutoDetach. Explicit detaches(ie: em.detach(..) ) will work as they always
> have before.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
