You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openjpa.apache.org by "Patrick Linskey (JIRA)" <ji...@apache.org> on 2007/07/20 22:06:06 UTC
[jira] Commented: (OPENJPA-290) Bulk updates and deletes ignore
vast swaths of OpenJPA architecture
[ https://issues.apache.org/jira/browse/OPENJPA-290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12514308 ]
Patrick Linskey commented on OPENJPA-290:
-----------------------------------------
When expected semantics cannot be performed in a bulk way, we should have an easy configuration option (ideally turned on automatically) to fall back to select-then-operate behavior.
> Bulk updates and deletes ignore vast swaths of OpenJPA architecture
> -------------------------------------------------------------------
>
> Key: OPENJPA-290
> URL: https://issues.apache.org/jira/browse/OPENJPA-290
> Project: OpenJPA
> Issue Type: Bug
> Components: jdbc
> Affects Versions: 0.9.0, 0.9.6, 0.9.7
> Reporter: Patrick Linskey
>
> OpenJPA's bulk update and delete semantics ignore a bunch of normal OpenJPA concepts, such as secondary tables and externalized values. The bulk operations support should be brought into line with these concepts, ideally in a way that reuses existing logic instead of emulating the same functionality.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.