When the parent entity is required, a new parent row can always be inserted.

More Questions from Data Models into Database Designs

• When the parent entity is required, cascading updates and cascading deletions should be allowed or the associated actions on the parent should be prohibited.
• An intersection table is required to represent M:N relationships.
• In a 1:1 relationship, the primary key placement is arbitrary.
• For every relationship, there are six possible sets of minimum cardinalities.
• Cascading updates refers to child rows being automatically deleted when a parent row is deleted.
• Surrogate keys have much meaning for users.
• When the parent entity is required, a new child row can always be inserted.
• When transforming an entity-relationship model into a relational database design, each entity is represented as a table.
• When the parent entity is required and the parent has a surrogate key, update actions can be ignored.
• An ideal primary key is short, numeric and seldom changing.

Discussion & Comments