Implementation of a university database using MySQL

• py -3 -m venv .venv
• .venv\scripts\activate # activate virtual environment
• Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy Unrestricted # run only if above line doesn't work
• pip install Flask
• pip(or pip3) install flask-mysqldb
• pip(or pip3) install python-dotenv
• pip(or pip3) install geopy
• pip3 install -r requirements.txt

Courses: records the courses taught at AH University
● course_id: int, auto_increment, unique, not NULL, PK (Primary Key)
● course_name: varchar(255), unique

Students: records the students that are enrolled at AH University
● student_id: int, auto_increment, unique, not NULL, PK (Primary Key)
● student_first_name: varchar(255), not NULL
● student_last_name: varchar(255), not NULL
● campus_id: int, not NULL, FK (Foreign Key)

Instructors: records the instructors that lecture at AH University
● instructor_id: int, auto_increment, unique, not NULL, PK (Primary Key)
● instructor_first_name: varchar(255), not NULL
● instructor_last_name: varchar(255), not NULL
● campus_id: int, FK (Foreign Key)

Campuses: records the campuses offered at AH University
● campus_id: int, auto_increment, unique, not NULL, PK (Primary Key)
● campus_name: varchar(255), unique, not NULL
● campus_city: text
● campus_country: text
● campus_online: boolean

Sections: records the sections of courses with its campus and instructor
● section_id: int, auto_increment, unique, not NULL, PK (Primary Key)
● course_id: int, not NULL, FK (Foreign Key)
● instructor_id: int, not NULL, FK (Foreign Key)
● campus_id: int, not NULL, FK (Foreign Key)

The Entities are related as follows:

1. A student can register for zero or more sections.
2. A section can have zero or more students enrolled in it.
3. A student can enroll in exactly one campus.
4. A campus can have zero or more students enrolled.
5. A course can be available at one or more campuses.
6. A campus can have one or more courses.
7. A course can have one or more sections.
8. A section can have exactly one course.
9. An instructor can teach at one campus at most.
10. A campus can have one or more instructors.
11. An instructor can teach zero or more sections.
12. A section can be taught by exactly one instructor.
13. A section can be available at exactly one campus.
14. A campus can have one or more sections.

1. 1 to M: Campuses and Students. A student must be enrolled in exactly one campus, but a campus can have many students enrolled. This is implemented with campus_id as a FK (Foreign Key) inside of Students.
2. 1 to M: Campuses and Instructors. An instructor can teach at one campus at most, but a campus can have many instructors. This is implemented with campus_id as a FK (Foreign Key) inside of Instructors.
3. 1 to M: Courses and Sections. A course can have many sections, but a section can have exactly one course. This is implemented with course_id as a FK (Foreign Key) inside of Sections.
4. 1 to M: Instructors and Sections. An instructor can teach many sections, but a section can have exactly one instructor. This is implemented with instructor_id as a FK (Foreign Key) inside of Sections.
5. 1 to M: Campuses and Sections. A section can only be available at exactly one campus, but a campus can have many sections. This is implemented with campus_id as a FK (Foreign Key) inside of Sections.
6. M to M: Students and Sections. A student can register for many sections, and a section can include many students. This is implemented by a separate relationship or intersection table that contains a listing of which sections students are registered in and which students are enrolled in each section. For example: section_id (FK) student_id (FK)
7. M to M: Courses and Campuses. A course can be available at many campuses, and a campus can have many courses. This is implemented by a separate relationship or intersection table that contains a list of which courses are offered at each campus and which campuses a course is taught at. For example: course_id (FK) campus_id (FK)