[
https://issues.apache.org/jira/browse/TORQUE-9?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13051776#comment-13051776
]
Thomas Fox commented on TORQUE-9:
---------------------------------
Not all SQL statements which are working for "select then delete" work for a
direct "delete from XXX", e.g. joins do not work at least for oracle and mysql.
For these cases, a simple workaround should be given by
List<X> xList = XPeer.doSelect(criteria);
XPeer.doDelete(xList);
The latter method still needs to be implemented.
> BasePeer.doDelete() should not load the datasets to delete them
> ----------------------------------------------------------------
>
> Key: TORQUE-9
> URL: https://issues.apache.org/jira/browse/TORQUE-9
> Project: Torque
> Issue Type: Improvement
> Components: Runtime
> Affects Versions: 3.0, 3.1, 3.1.1, 3.2
> Reporter: Thomas Fox
>
> In BasePeer.doDelete, all datasets which should be deleted are loaded. This
> introduces significant overhead, but is only necessary for cascading deletes.
> For non-cascading deletes, the datasets should not be loaded, but a "delete
> from ..." statement should be issued instead.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
