From the course: Relational Databases Essential Training
Unlock the full course today
Join today to access over 24,100 courses taught by industry experts.
Relationship optionality and cardinality
From the course: Relational Databases Essential Training
Relationship optionality and cardinality
- [Instructor] Once two tables are related together, you can start to think about the minimum number of records that can be related and the maximum number. In relational database terminology, these are called optionality and cardinality. Optionality is a measure of the minimum number of records that can be associated between two ends of a relationship. This number is usually either zero or one, and it can be thought of as the difference between must and might. For example, if a customer must have at least one order, then the optionality is one. That indicates a situation where your business rules dictate a requirement that every customer has at least one order before their record can be created. The minimum number allowed is one, so the optionality is one. On the other hand, if a customer might have an order, the optionality is zero. This indicates a situation where a customer's record can be created before…
Practice while you learn with exercise files
Download the files the instructor uses to teach the course. Follow along and learn by watching, listening and practicing.
Contents
-
-
-
-
-
-
(Locked)
Relate tables with foreign keys4m 57s
-
(Locked)
Diagram a relationship2m 42s
-
(Locked)
Relationship optionality and cardinality5m 15s
-
(Locked)
One-to-many relationships2m 10s
-
(Locked)
One-to-one relationships1m 10s
-
(Locked)
Many-to-many relationships2m 21s
-
(Locked)
Self joins2m 17s
-
(Locked)
Cascade changes2m 17s
-
(Locked)
-
-
-
-