Course Content
Detailed Content of Database Management System
0/1
About Lesson


| StudentID (PK) |   Name    |   Age   |  Major   |
|----------------|-----------|---------|----------|
|      101       |  Alice    |   20    |   Math   |
|      102       |  Bob      |   22    | Physics  |
|      103       |  Carol    |   21    | English  |

In this example, “Student” is a strong entity with the primary key attribute “StudentID” uniquely identifying each student.

| StudentID (FK) | CourseID (FK) |   Grade   |
|----------------|---------------|-----------|
|      101       |      201      |     A     |
|      102       |      202      |     B     |
|      103       |      203      |     A-    |

In this example, “Course Enrollment” is a weak entity that relies on the combination of “StudentID” (foreign key referring to the “Student” entity) and “CourseID” (foreign key referring to the “Course” entity) to uniquely identify each enrollment. The combination of these attributes acts as a composite or partial key.

In summary:

  1. Strong entities can be uniquely identified by their own attributes and have a primary key.
  2. Weak entities cannot be uniquely identified by their attributes alone and depend on a related strong (parent) entity for identification, typically through a discriminator and the parent’s key.