As a developer, I want to handle mySQL table issues that might occur in the future and their scalability.
Technical Task:
Re-evaluate the current professorDB table (or any future tables created). Consider the following edge case:
John Doe is a ME professor with a 3.9 Rate My Professor (RMP) score.
John Doe is a CS professor with a 1.2 RMP score.
How would the mySQL database add the two professors into the database? How would the mySQL database tell which professor is the intended professor when searching for John Doe?
Possible solution: Change the primary key to be a row that autoincrements to allow the mySQL database to add the two professors. To tell the difference between the two professors, look into whether the department where that professor works can be obtained?
Acceptance Criteria:
The edge case described above is resolved.
mySQL schemas are evaluated to ensure no future issues and created in such a way to be scalable (Is there a way to optimize how we store data?)
User Story
As a developer, I want to handle mySQL table issues that might occur in the future and their scalability.
Technical Task:
How would the mySQL database add the two professors into the database? How would the mySQL database tell which professor is the intended professor when searching for John Doe?
Possible solution: Change the primary key to be a row that autoincrements to allow the mySQL database to add the two professors. To tell the difference between the two professors, look into whether the department where that professor works can be obtained?
Acceptance Criteria: