comanage-dev - Re: [comanage-dev] Cascading a delete
Subject: COmanage Developers List
List archive
- From: Benn Oshrin <>
- To: Scott Koranda <>
- Cc: comanage-dev <>
- Subject: Re: [comanage-dev] Cascading a delete
- Date: Wed, 12 Oct 2011 14:05:42 -0400
On 10/12/11 1:43 PM, Scott Koranda wrote:
* For in-progress petitions, we can delete any collected attribute.Could we instead just ignore the collected attribute value?
Sure.
* For completed petitions, do we want to maintain referential
integrity (or even maintain the petition itself) for historical
purposes?
I would argue yes. People are going to want to do that as the
size and complexity of the VO increases.
If so, does that mean we never delete CO Enrollment
Attributes, only set them to some Inactive status?
Yes, I think so.
There's a similar question for the CO Enrollment Flows, too.Set to inactive.
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.
-Benn-
- [comanage-dev] Cascading a delete, Benn Oshrin, 10/12/2011
- Re: [comanage-dev] Cascading a delete, Scott Koranda, 10/12/2011
- Re: [comanage-dev] Cascading a delete, Benn Oshrin, 10/12/2011
- Re: [comanage-dev] Cascading a delete, Benn Oshrin, 10/13/2011
- Re: [comanage-dev] Cascading a delete, Benn Oshrin, 10/12/2011
- Re: [comanage-dev] Cascading a delete, Scott Koranda, 10/12/2011
Archive powered by MHonArc 2.6.16.