These two papers must be purchased
(and read) together for double the price of an individual paper.
As a concept, first normal form (1NF) is absolutely
fundamental in the database field, and yet it isn't at all well understood by
the IT community at large (at least if the available literature is anything to
go by).
This two-part article represents an attempt to set the record
straight; it offers a clear, precise, and accurate explanation of 1NF, and it
explores some of the many implications of that concept.
C. J. DATE: WHAT FIRST NORMAL FORM REALLY
MEANS
·
INTRODUCTION
·
SOME PRELIMINARIES
·
DATA VALUE ATOMICITY"
·
RELATION-VALUED ATTRIBUTES
·
DOMAINS CAN CONTAIN ANYTHING!
·
RVA’S MAKE OUTER JOIN UNNECESSARY
·
RVA’S IN BASE TABLES?-THE BAD NEWS
·
RVA’S IN BASE TABLES?-THE GOOD NEWS
·
A REMARK ON "NF2 RELATIONS"
·
A DEFINITION
·
CONCLUDING REMARKS
·
APPENDICES A-E
F.
PASCAL: WHAT FIRST NORMAL FORM MEANS NOT
The purpose of this paper is to use the correct 1NF concept
to debunk fallacies prevalent in the industry. In particular, the paper aims to
dispel claims that so-called “multivalue database” technology violates neither
1NF, nor the relational model, and that it has advantages over the latter,
rather than drawbacks.
·
THE KISS PRINCIPLE
·
LET’S NOT GET PHYSICAL
·
OTHER MISCONCEPTIONS
·
IN THE EYE OF THE BEHOLDER
·
NO VALUE IN MULTI-VALUE
·
CONCLUSION
·
REFERENCES
Use of Materials Policy
PRICING AND ORDERING
