Re: Avoiding collection of entities
I think he is telling that I should avoid entities of multiple entities because he mentioned another example after "Inventory" example and said you can not represent a medical history of a patient with one entity because it consists of "appointments" as an entity and "treatments" which is another entity.
- he is talking about designing a relational database for OLTP not OLAP as I remember.
thanks for subscribing.
Subject
Written By
Posted
Re: Avoiding collection of entities
January 16, 2018 12:20PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.