True, good point -- ok, will leave delete as-is for now, and we can discuss
how best to work w/ the field as the use cases come up -- thanks for the
perspective!


On Wed, May 7, 2014 at 12:28 PM, David Ormsbee <notifications@github.com>wrote:

> In lms/djangoapps/api_manager/models.py:
>
> > @@ -79,12 +78,9 @@ class LinkedGroupRelationship(models.Model):
> >      to_group_relationship = models.ForeignKey(GroupRelationship,
> >                                                related_name="to_group_relationships",
> >                                                verbose_name="To Group")
> > -    record_active = models.BooleanField(default=True)
>
> I think it might be simpler to think of record_active as just another
> attribute, and not conflate it with delete. So you could, for instance do
> an update that sets that attribute to False. Otherwise, REST semantics
> get kinda weird (if not active = delete, then trying to reactivate involves
> a PUT to an address that should 404... etc.)
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/edx-solutions/edx-platform/pull/41/files#r12387120>
> .
>



-- 
Matthew Drayer
Solutions Architect
edX | MIT
mattdrayer@edx.org