[
https://issues.apache.org/jira/browse/OPENJPA-2017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Zowalla resolved OPENJPA-2017.
--------------------------------------
Resolution: Fixed
Already fixed on master: 31c0249e1 is on master. AutoDetach.java:50-53 defines
DETACH_NONE, StateManagerImpl.java:3349 skips proxying, and
BrokerImpl.java:5695 refuses to combine NONE with other options, as requested.
Closing; please reopen if this still happens with OpenJPA 4.x.
> Improve batch insertion performance
> -----------------------------------
>
> Key: OPENJPA-2017
> URL: https://issues.apache.org/jira/browse/OPENJPA-2017
> Project: OpenJPA
> Issue Type: New Feature
> Components: kernel
> Affects Versions: 2.1.1, 2.2.0
> Reporter: Pinaki Poddar
> Assignee: Pinaki Poddar
> Priority: Major
>
> Batch loading data is a common use case. Often, the user would not refer to
> the managed instances after the loading session. However, the runtime, by
> default, spends time in detaching the managed instances by creating/removing
> proxy or retaining state as per the configured options.
> An option should be provided to bypass these operations per persistence
> context basis.
> AutoDetach.NONE could be a possibility. This option will be exclusive i.e. it
> can not be specified with any other AutoDetach options. The NONE option will
> bypass proxying the fields at the transaction boundary or close.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
