- Design each relation schema so that it is easy to explain its meaning. Intuitively, each schema should correspond to one entity or one relationship type in the real life.
- Design relation schema so that no insertion, deletion, or modification anomalies are present.
Thursday, 9 October 2008
Database: Functional Dependencies and Normalization
Database Design Guideline
Subscribe to:
Posts (Atom)
-
Could not extract response: no suitable HttpMessageConverter found for response type [class dk.enettet.evu.core.model.Address] and content ... -
First time met this hibernate exception. I think this issue should due to one to one relationship. One driver has one car; one car has on...
-
A large object refers to the entity property that is modified by @Lob. It may be persisted in several records. However, in database manage...