In a one-to-many (1:N) relationship, what do we call the entity on the many side?

Introduction / Context:
One-to-many relationships are ubiquitous: one customer has many orders, one department has many employees. Understanding the parent–child terminology clarifies referential integrity and foreign key placement.

Given Data / Assumptions:

• The relationship is 1:N (one parent to many children).
• We need the role name for the N-side entity.
• Conventional ER terminology is assumed.

Concept / Approach:
In 1:N, the single-instance side is the parent, and the multiple-instances side is the child. In the relational schema, the child table typically contains the foreign key referencing the parent's primary key.

Step-by-Step Solution:

Verification / Alternative check:
Most modeling notations and RDBMS textbooks use this nomenclature for clarity when mapping relationships to tables.

Why Other Options Are Wrong:
Parent: Refers to the one side.
Instance: A specific occurrence, not a role.
Subtype: Part of supertype–subtype, unrelated to 1:N roles.
Associative: Typically resolves M:N relationships.

Common Pitfalls:
Putting the foreign key on the parent instead of the child leads to incorrect optionality and duplication issues.

Final Answer:
child