Update anomalies

GUIDELINE 3: Relations should be designed such that their tuples will have as few NULL values as possible  Attributes that are NULL frequently could be placed in separate relations (with the primary key)  Reasons for nulls: attribute not applicable or invalid attribute value unknown (may exist) value known to exist, but unavailable

60p thienthanoze 12-11-2012 53 3   Download

For each weak entity type W in the ER schema with owner entity type E, create a relation R and include all simple attributes (or simple components of composite attributes) of W as attributes of R. In addition, include as foreign key attributes of R the primary key attribute(s) of the relation(s) that correspond to the owner entity type(s). The primary key of R is the combination of the primary key(s) of the owner(s) and the partial key of the weak entity type W, if any.

32p thienthanoze 12-11-2012 55 2   Download