-
Notifications
You must be signed in to change notification settings - Fork 4
Redesign the database #8
Copy link
Copy link
Open
Labels
databaseDatabase-related issuesDatabase-related issuesdesignDesign-related issues (System design, database design, UI/UX design)Design-related issues (System design, database design, UI/UX design)enhancementNew feature or requestNew feature or requesthard
Metadata
Metadata
Assignees
Labels
databaseDatabase-related issuesDatabase-related issuesdesignDesign-related issues (System design, database design, UI/UX design)Design-related issues (System design, database design, UI/UX design)enhancementNew feature or requestNew feature or requesthard
Is your feature request related to a problem? Please describe.
Right now, we are structuring the database in the flow of user > course > assessment. This might not be an ideal design for the database (e.g. if we want to query a course, you need to go over each of user data record and find it)
Describe the solution you'd like
We probably want to create design a new database system, where we can effectively query (i.e. reduce number of queries) the existing courses from the database. One possible way to do this is to have separate documents/tables for users, courses, and assessments. But you want to take a look at data modelling.
Resources
Additional context

Example of how the database is structured now: