I am a beginner in the database. I don't know how to design or solve the problem. Select "Major" and return to the curriculum. How should we design each table. How should I get back to the course schedule and generate a weekly schedule? Now I designed the system table (Department ID, Department name) professional table (Professional ID, professional name, department... my problem
Beginner database, do not understand design, solution.
Select "Major" and return to the curriculum
How to Design tables.
How should I get back to the course schedule and generate a weekly schedule?
Now I designed
Department table (Department ID, Department name)
Professional table (Professional ID, professional name, department ID)
Class table (class ID, class name, professional ID)
Course table (table ID, course name, class ID)
Reply content: my questions
Beginner database, do not understand design, solution.
Select "Major" and return to the curriculum
How to Design tables.
How should I get back to the course schedule and generate a weekly schedule?
Now I designed
Department table (Department ID, Department name)
Professional table (Professional ID, professional name, department ID)
Class table (class ID, class name, professional ID)
Course table (table ID, course name, class ID)
If it is me, I will create a dedicated link form to store various IDS to represent the corresponding link;
Each table that represents a transaction only contains attributes related to the transaction.
Department table (Department ID, Department name)
Professional table (Professional ID, professional name)
Class table (class ID, class name)
Course table (table ID, course name)
Relational table (relational ID, System ID, professional ID, class ID, table ID)
This facilitates maintenance and provides clear logic.