School
students, teachers, courses, classes and results. 9 tables, 32 columns, no data.
The map
Each line runs from a linking column (N) to the key it points at (1). The same tables are listed below as text.
The tables
students
idbigintPKfull_namevarchar(200) requiredborn_ondateemailvarchar(255)
teachers
idbigintPKfull_namevarchar(200) requiredemailvarchar(255)
departments
idbigintPKnamevarchar(200) requiredhead_teacher_idbigint→ teachers
courses
idbigintPKtitlevarchar(200) requiredteacher_idbigint→ teachers requireddepartment_idbigint→ departments required
classrooms
idbigintPKroom_codevarchar(20) requiredseatsinteger required
sessions
idbigintPKcourse_idbigint→ courses requiredclassroom_idbigint→ classrooms requiredstarts_attimestamptz required
enrolments
idbigintPKstudent_idbigint→ students requiredcourse_idbigint→ courses requiredgradenumeric(12,2)
attendance
idbigintPKstudent_idbigint→ students requiredsession_idbigint→ sessions requiredpresentboolean required
audit_log
attimestamptz requiredwhovarchar(100) requiredwhattext
What you could look at in SSDO
- Ask what depends on students.
- enrolments joins students and courses: see it as a link table on the Map.
- audit_log has no primary key: Review describes what that means.
Create a free workspace and open this sample All samples
PK is a primary key. “→ table” is a link (a foreign key) to that table. This page is a description of a structure we wrote; it holds no rows.