db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fox (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TORQUE-165) Implement cascading deletes
Date Fri, 15 Jul 2011 15:48:00 GMT

    [ https://issues.apache.org/jira/browse/TORQUE-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13066021#comment-13066021

Thomas Fox commented on TORQUE-165:

Cascading deletes for known foreign keys is quite easy to implement and one could imagine
use cases where one would want to determine at run time whether one wants to have a cascaded
delete or not (though I do not currently can imagine one). 
The reason I entered this issue is that there was a sort of cascading delete implemented in
3.3 but I never found out how it worked and whether it worked at all (I 'd bet on the second),
so I thought it was no good dropping out features from 3.3.

But I'm ok with not implementing cascading deletes in Torque.
However, to have a clean API, this would mean to drop the cascade flag on criteria.

If nobody speaks up in favour of this feature in a few days I'll remove the cascade flag on
criteria and close the issue as wontfix.

> Implement cascading deletes
> ---------------------------
>                 Key: TORQUE-165
>                 URL: https://issues.apache.org/jira/browse/TORQUE-165
>             Project: Torque
>          Issue Type: Improvement
>            Reporter: Thomas Fox
>            Assignee: Thomas Fox
> If the flag criteria.cascade is set to true and a detelete() method is called on a peer
class, all rows ehich are referenced by the deleted rows should be deleted as well, including
rows which are referenced indirectly.

This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org

View raw message