Closed YaleChen299 closed 10 months ago
I'm not too sure, what's the rationale of using the course ID as a primary key, especially since we already have an ID column? What would happen if a course wants to have multiple groups in the future?
If it's simply to enforce the uniqueness, I would argue it's better to create a unique index, and just drop/modify it later if we want to support the has-many relationship.
My main thought process is that this feature is just one for some default view just like the last_viewed_course
in the main backend, so we just need one default one that ties to the course. That's why I think it is just a table that uses course as a key. I don't think we really need that many course to one group feature though. When we have more groups the group is just like a channel that you subscribed to. We just need to show all groups joined by a user and the user can switch group.
Adds the mapping between courses in the main backend to the groups in the stories backend.