openjpa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Curtis (JIRA)" <j...@apache.org>
Subject [jira] Commented: (OPENJPA-1545) Add new Detach processing
Date Wed, 03 Mar 2010 19:24:27 GMT

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

Rick Curtis commented on OPENJPA-1545:
--------------------------------------

Committed code changes, doc, and a simple UT to trunk.

Additional unit tests still need to be created. 

> Add new Detach processing
> -------------------------
>
>                 Key: OPENJPA-1545
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-1545
>             Project: OpenJPA
>          Issue Type: Improvement
>          Components: performance
>            Reporter: Rick Curtis
>            Assignee: Rick Curtis
>         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.


Mime
View raw message