Closed kkevlar closed 5 years ago
While redundant, there's no pressing reason to take it out if the DB sorting stuff relies on it. A course entity can keep both the name "CSC309" and have a department string, but that means that we need logic to handling that parsing.
This shouldn't be done. It will break the methods in ClassDB that rely on the department field for sorting and filtering