In data modeling, what do we call a relationship where one record of a given type can be associated with more than one record of another type (e.g., one customer has many orders)?

Introduction / Context:
Accurately naming relationships is essential for normalization and key design. The directionality and cardinality (one vs. many) influence primary/foreign key placement, indexing, and how applications query and display related data (master-detail forms, joins, and cascades).

Given Data / Assumptions:

• One record in entity A relates to multiple records in entity B.
• The example “one customer has many orders” is a classic pattern.
• We are identifying the correct cardinality label.

Concept / Approach:
A one-to-many relationship exists when a single parent instance connects to multiple child instances. Implemented relationally, the child table contains a foreign key to the parent. This structure supports efficient querying and referential integrity rules (e.g., ON DELETE RESTRICT/SET NULL/CASCADE) depending on business needs.

Step-by-Step Solution:

Verification / Alternative check:
ER diagrams and schema examples consistently label Customer→Order as one-to-many, confirming the standard term.

Why Other Options Are Wrong:

• One-to-one: Each side has at most one counterpart—does not match.
• Many-to-one: Inverse perspective from the child to the parent.
• Many-to-many: Requires an associative/junction table—different structure.
• None: Incorrect, as the standard term exists.

Common Pitfalls:
Confusing many-to-one with one-to-many due to perspective; forgetting foreign key placement on the many side.

Final Answer:
One-to-many relationship