The createDBManager function in prepareClassDB has an unused parameter: managerName.
The simple fix is to remove the parameter, which might be all that is done for M1.
However, the parameter exists to match the parameters of createInstructor and createStudent. Those functions store xyName in the classdb.Instructor and classdb.Student tables. However, there is no classdb.Manager table in which we could store the value of managerName in. We may wish to consider whether we should have a classdb.Manager table, or possibly even remove the classdb.Instructor table. Currently, DBManager is not consistent with the other roles, and almost appears like it is an afterthought.
The
createDBManager
function inprepareClassDB
has an unused parameter:managerName
.The simple fix is to remove the parameter, which might be all that is done for M1.
However, the parameter exists to match the parameters of
createInstructor
andcreateStudent
. Those functions store xyName in theclassdb.Instructor
andclassdb.Student
tables. However, there is noclassdb.Manager
table in which we could store the value ofmanagerName
in. We may wish to consider whether we should have aclassdb.Manager
table, or possibly even remove theclassdb.Instructor
table. Currently, DBManager is not consistent with the other roles, and almost appears like it is an afterthought.