Group:
data type
Topic:
business application language
Topic:
data as a named set of data objects
Topic:
data record
Topic:
database implementation
Topic:
database schema
Topic:
forms as a UserInterface
Topic:
information as facts
Topic:
namespace
Topic:
relational database
Topic:
representing a relationship
Topic:
undefined, null, and other signal values
| |
Summary
Hierarchical, relational, and network models are variations of the data record. A database record is a fixed pattern of fields. The type, name, and meaning of a field is part of the database schema. Ideally it will aggregate all facts about an entity but often the relationship is tenuous. (cbb 1/90)
Subtopic: data record model 
| Quote: data records useful for providing a view of data and for providing authorized access to a data subset [»kentW_1978]
| | Quote: data records consist of a fixed pattern of data types [»shimBE4_1987]
| | Quote: data records work best when all entities of a type have the same characteristics [»kentW_1978]
| | Quote: a record file is a collection of fields; can display records in a table or as a form with fields; query by example [»smitDC4_1982]
| | Quote: hierarchical, relational, and network models are variations of the data record model [»kentW_1978]
|
Subtopic: data schema, what how why
| Quote: a data dictionary documents each field by what it is, how it's represented, and why it's there; ties conceptual schema to database [»kentW1_1985]
| | Quote: describe fields of a data record by entity type, representation type, and relationship to other fields; what, how, and why [»kentW1_1985]
|
Subtopic: data field as the real world
| Quote: a field in a record contains a character string that represents something in the real world; e.g., a color [»kentW1_1985]
| | Quote: any of the things in the real world can be represented by different strings in different fields
|
Subtopic: data record as entity
| Quote: data records are entities; inserted, deleted, retrieved, identifies, typed [»kentW1_1985]
|
Subtopic: data record as facts, connections
| Quote: a record represents an aggregate of facts, i.e., connections between fields [»kentW1_1985]
| | Quote: the meaning of a field in a data record is usually implicit; e.g., joe smith and 95 [»kentW_1978]
| | Quote: much of the meaning of a data record is supplied by users and procedures [»kentW_1978]
| | Quote: a record stores multiple, single-valued facts about the primary key, or it stores a multi-valued/n-ary fact [»kentW1_1985]
| | Quote: when possible, a data record should aggregate all facts about an entity [»kentW1_1984]
|
Subtopic: normalization
| Quote: a reducible record can be decomposed such that the reconstruction does not introduce spurious data [»kentW_1978]
|
Subtopic: business data
| Quote: business programming needs data records, decimal arithmetic, report generation, large databases [»glasRL9_1997]
| | Quote: business data is heterogeneous and hierarchical: fixed-length strings, variable-length strings, and decimal numbers [»glasRL9_1997]
|
Subtopic: naming
| Quote: name of a relationship is not part of a data record; nor is the type of an entity [»kentW_1978]
| | QuoteRef: sammJE5_1962 ;;139 Cobol's record components may have more than one name
|
Subtopic: limitations of data records
| Quote: use data records for efficiency; a data record is not a natural model [»kentW_1978]
| Quote: records can not correspond to major entities; what are they, drifting assignment, relationships vs. attributes
[»kentW1_1984]
|
Related Topics
Group: data type (34 topics, 730 quotes)
Topic: business application language (11 items)
Topic: data as a named set of data objects (22 items)
Topic: data record (57 items)
Topic: database implementation (18 items)
Topic: database schema (29 items)
Topic: forms as a UserInterface (11 items)
Topic: information as facts (21 items)
Topic: namespace (19 items)
Topic: relational database (35 items)
Topic: representing a relationship (28 items)
Topic: undefined, null, and other signal values
(34 items)
|
