Relational vocabulary: in a relation, are rows sometimes informally called “records” (even though the formal term is “tuples”)?
-
ACorrect
-
BIncorrect
-
COnly in hierarchical databases
-
DOnly in object databases
Answer
Correct Answer: Correct
Explanation
Introduction / Context:Different data models use different vocabulary. In the relational model, the formally correct term for a row is “tuple,” but many tools, textbooks, and practitioners informally say “record.” This question asks whether that informal usage is sometimes applied.
Given Data / Assumptions:
- Relational theory uses “relation/attribute/tuple.”
- Legacy and practical usage often says “table/column/row/record.”
- The statement explicitly says “sometimes called ‘records’.”
Concept / Approach:While “record” comes from earlier file systems and hierarchical models, it remains common in practice and documentation to refer to a relational row as a record. Therefore, the statement is acceptable as phrased (“sometimes called”). It would be imprecise to assert that “record” is the formal term, but acknowledging common usage is correct.
Step-by-Step Solution:
Identify formal term: tuple.Recognize common term: record or row in many tools and UIs.Conclude: the statement is correct as it qualifies “sometimes called.”Verification / Alternative check:Check database client software and UI labels; you will often see “records returned.”
Why Other Options Are Wrong:
- “Incorrect” would deny the widespread informal usage acknowledged by the statement.
- References to other models (hierarchical or object) are not required; this is about terminology breadth.
Common Pitfalls:Insisting that only textbook terminology is acceptable in all contexts; in exams, read qualifiers like “sometimes” carefully.
Final Answer:Correct