COmanage Developers List

[Benn Oshrin <>]

On 10/12/11 2:05 PM, Benn Oshrin wrote:
> OK, so I think the idea is that delete honors cascade (so if you delete
> a CO Enrollment Flow all the related data is deleted as well) BUT that
> this is not recommended and you get a warning if you try to do it.
>
> Sort of like deleting a CO... you can do it, but you generally shouldn't.

And more generally... we probably want to do one or both of the following:

 (1) On any delete that can trigger a cascade, warn about what
     cascaded data elements would also get deleted.

 (2) On any delete that can trigger a cascade, "fix" the data to
     minimize the impact. For example, if a delete would touch a
     co_petition_history_record because the actor is being deleted,
     just blank the link instead of deleting the entire record.

-Benn-