Three main paradigms of Oracle

Paradigm: A rule for designing a database definition,

Three paradigms, flexible use, human thought is living
A paradigm
1, there is no redundant data
Records in the same table cannot have duplicate----so the primary key (must have)
2, each field must be non-divided information (columns are not allowed to be divided)
Depending on the situation, such as a social security number, save a lot of information, but in fact, the whole of the ID card is saved, this time there is no need to split
In another case, you need to save two of the same type of data, and then subdivide it according to the specific situation
Redundancy of information Another situation:
One field is age, one field is birthday, information content is redundant
Two paradigms (Prerequisites: First in accordance with the first paradigm):
Eliminate partial dependencies
Mainly for many-to-many association tables

The third paradigm (premise: First satisfies the second paradigm):
Eliminate delivery dependencies
Mainly for a one-to-many relationship

Three main paradigms of Oracle