Abstract
The desirability of acyclic database scheme is well argued. When a scheme is described by multivalued dependencies, acyclicity means that the dependencies do not split each other's left-hand side and do not form intersection anomalies. Shown is that if the second condition fails to hold, the scheme can be amended so that it holds. The basic step is to add one attribute and some dependencies to resolve one intersection anomaly. This step generates an extension of the given scheme in which the anomaly does not exist. Analyzed is the repetitive use of the basic step and proven is that the transformation so defined removes all intersection anomalies. Finally characterized are a class of attributes that can be removed from the final scheme, leaving it acyclic.
Original language | English |
---|---|
Title of host publication | Unknown Host Publication Title |
Publisher | ACM |
Pages | 340-357 |
Number of pages | 18 |
ISBN (Print) | 0897910974 |
State | Published - 1983 |
Externally published | Yes |