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-2165) Allow lazy proxy relationships to add or remove elements without triggering a load
Date Wed, 05 Feb 2014 22:50:12 GMT

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

Rick Curtis commented on OPENJPA-2165:
--------------------------------------

Hey Jeremy, is there any further work to be completed on this JIRA?

> Allow lazy proxy relationships to add or remove elements without triggering a load
> ----------------------------------------------------------------------------------
>
>                 Key: OPENJPA-2165
>                 URL: https://issues.apache.org/jira/browse/OPENJPA-2165
>             Project: OpenJPA
>          Issue Type: New Feature
>          Components: jdbc, kernel, performance
>    Affects Versions: 2.2.1, 2.3.0
>            Reporter: Jeremy Bauer
>            Assignee: Jeremy Bauer
>
> When adding or removing elements from a non-database-ordered (no order by or order column
- which require strict order to be maintained) lazy proxied collection which is a relationship
to other entities, OpenJPA loads the collection before performing the operation.  This can
be very expensive if an operation is only adding or removing items from the collection.  I
created a feature that, when switched on, allows non-indexed add and remove operations to
be performed on a collection without triggering a load.  The collection will get loaded (and
reconciled, if necessary) when an operation is performed that requires a load, such as iteration,
size, isEmpty, etc.  Currently, the feature can be enabled for the using this new attribute
on the ProxyManager.
> <property name="openjpa.ProxyManager" value="delayCollectionLoading=true"/>
> The basics have been added to field mappings/metadata such that this could be enabled
on a per-field basis in the future.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message