GitHub PushEvent at 2014-10-15 19:02:27
Repository: acj-versus
Actor: mwytang
Payload: {"shas":[["5c7bf402f92f1bd0874e59aec653767daf76fae7","629d64dce97822b09d2047a7cdebcfbe55c64f3e@ubc.ca","refactored group member model\n\nAfter discussion, it was decided that it would be better if the group\nmember model is related to Users instead of CoursesAndUsers. Since\nthe feature is still under development, I just dropped the\nGroupsAndCoursesAndUsers model and created the GroupsAndUsers model.\nAnother reason was it was not possible to write a generic script to\ndrop the foreign key constraint for coursesandusers_id because we need\nthe name, which is autogenerated and may be different depending on the\nSQL server being used\n\nOther than minor refactoring to change the model used from\nGroupsAndCoursesAndUsers to GroupsAndUsers and coursesandusers_id to\nusers_id, I also did the following:\n\n- removed the requirement that the user has to be enroled in the course\nto be dropped from a group. The reason is it also makes sense to drop\na user from a group even if they are no longer enroled in the course.\n- moved the groups relationship to users, which will list all of the\nactive GroupsAndUsers object the user is related to.\n- under CoursesAndUsers, I created a hybrid property that filters the\nlist of groups in Users to only list the groups in the course\n- refactored tests to reflect the changes made","mwytang",true]],"size":1,"ref":"refs/heads/develop","head":"5c7bf402f92f1bd0874e59aec653767daf76fae7"}