A relational model of data for large shared data banks
Communications of the ACM
File definition and logical data independence
SIGFIDET '71 Proceedings of the 1971 ACM SIGFIDET (now SIGMOD) Workshop on Data Description, Access and Control
Storage structure and physical data independence
SIGFIDET '71 Proceedings of the 1971 ACM SIGFIDET (now SIGMOD) Workshop on Data Description, Access and Control
Normalized data base structure: a brief tutorial
SIGFIDET '71 Proceedings of the 1971 ACM SIGFIDET (now SIGMOD) Workshop on Data Description, Access and Control
A data base sublanguage founded on the relational calculus
SIGFIDET '71 Proceedings of the 1971 ACM SIGFIDET (now SIGMOD) Workshop on Data Description, Access and Control
File definition and logical data independence
SIGFIDET '71 Proceedings of the 1971 ACM SIGFIDET (now SIGMOD) Workshop on Data Description, Access and Control
Armstrong axioms and Boyce-Codd-Heath Normal Form under bag semantics
Information Processing Letters
The boyce-codd-heath normal form for SQL
WoLLIC'11 Proceedings of the 18th international conference on Logic, language, information and computation
Conceptual Modelling and Its Theoretical Foundations
A normal form for preventing redundant tuples in relational databases
Proceedings of the 15th International Conference on Database Theory
Bibliography on data base structures
ACM SIGMIS Database
| Hi-index | 0.00 |
This paper is written within the context of a relational data base model as presented by E. F. Codd in [1]. It also serves as a companion paper to his paper [2]. The central thesis is that a file operation should not produce unexpected 'side effects' in order to maintain a restriction (such as one-one, or many-one) on the file. Any file operation which would violate a restriction for some possible data is called 'violative'. It is determined which cases of the file operations WRITE, REWRITE and DELETE are violative. We argue that most violative file operations should be rejected. Instead, the equivalent operations should be carried out on projections in E. F. Codd's 'third normal form' in order to alleviate the necessity for spurious side effects. It is therefore convenient for the programmer to be able to refer directly to these projections by name and for the data management system to allow operations on them. This provides further justification to that in [2] for modelling the data base interface between programmer and data management system in terms of relations in 'third normal form'.