Because of referential integrity, before any row can be entered into the SECTION table, the CourseID to be entered must already exist in the COURSE table. Write an SQL assertion that will enforce this constraint.

The class scheduling 3NF relations along with some sample data shown in Figure 6-10. Not shown in this figure are data for an ASSIGNMENT relation, which represents a many-to-many relationship between faculty and sections.

Transcribed Image Text:

STUDENT (StudentID, StudentName) QUALIFIED (FacultylD, CourselD, DateQualified) StudentID StudentName FacultylD CourselD DateQualified 38214 Letersky Altvater 2143 ISM 3112 9/1988 54907 2143 ISM 3113 9/1988 66324 Aiken 3467 ISM 4212 9/1995 70542 Marra 3467 ISM 4930 9/1996 4756 ISM 3113 9/1991 4756 ISM 3112 9/1991 .. FACULTY (FacultyID, FacultyName) SECTION (SectionNo, Semester, CourselD) FacultyID FacultyName SectionNo Semester CourselD 2143 Birkin 2712 1-2008 ISM 3113 3467 Berndt 2713 1-2008 ISM 3113 4756 Collins 2714 1-2008 ISM 4212 2715 1-2008 ISM 4930 .. COURSE (CourselD, CourseName) REGISTRATION (StudentID, SectionNo, Semester) CourselD CourseName StudentID SectionNo Semester ISM 3113 ISM 3112 Syst Analysis Syst Design Database Networking 38214 2714 2714 1-2008 1-2008 54907 54907 ISM 4212 2715 1-2008 ISM 4930 66324 2713 1-2008 FIGURE 6-10 Class scheduling relations (missing ASSIGNMENT)