Relationship Model Flashcards
(47 cards)
Hierarchical Database
1970 IBM Information Management System
1:M relationship
A tree of linked records
child has only one parent (limitation)
Network Database
Intergrated Data Store
Child have multiple parents
Navigational Database
Move around in data via pointers or links
Relational Model
basic structure is the mathematical concept
Relation
Table
Storage
Relation
Abstract object
Heading (fixed)
Body (varies over time)
Table
Pictorial representation
Domain
Set of atomic values which specifies
name, data type and data format
Relation Heading
aka Relation schema
consist of a fixed set of attributes (R)
each attribute (column) corresponds to an underlying domain
Relation cardinality
number of tuples
Relation body
aka Relation instance
Relation instance
State of the relation at any point in time
Consist of tuples (rows)
Relation degree
no of attributes
Tuples in Relation
No duplicate Unique Inordered in a relation Attributes not ordered in a tuple Atomic (cannot be divided) Not multivalued
Functional Dependency
A set of attributes ‘A’ functionally determines an attribute ‘B’ if, and only if,
for each A value, there is exactly one value of B in the relation. It is
denoted as A → B
A determines B
B depends on A
Candidate key
Attribute or set of attributes which exhibits uniqueness at minimum (minimal superkey) - proper subset is not a superkey
Primary Key
One or more candidate key that is chosen to be a primary key (primary key or composite primary key)
Alternate Key
Remaining keys that are not the primary key
Composite key
A primary key comprising of many attributes
How to Select Primary Key
Unique
Nonintelligent
No change over time
Single attribute
Numeric
Security Compliant
Null
no value
Why Null
Value not applicable
Value unknown
Value does not exist
Value undefined
Relational database
A collection of normalised relations
Foreign Key
An attribute or set of attributes in a relation that exists in the same or another relation as a Primary Key
Referential Integrity
A foreign key value must either match the full primary key in a relation or be null