Store Candidate Information
Candidates send there CV's to respective organization. Then each organization transform this candidate data in to information. Then we provide 2 main services based on those information. One is
At the beginning we started with the one table , it was designed by looking at GUI of extracting
We can describe how to handle following synario. this means that when there is many to many relation, how do we go about addressing following situation.
One person can have many email addresses, and One email address can have many people.
So, when there are two persons for one email address , we can set the status of one email address to be inActive or Active while , for other person , this will be active email address. so , that is one thing we might have add new attribute to the middle table of many to many relation.
What is the next synario.
Lets say , There is a CV table and there is a person table. A person can have many cv's and a cv can have only one person, but that is not what is told by
Most important point is , CV table has an attribute for Recommended Person. This means that for tables are linked by two relations, so , one recommended person can have many cv's and cv can have may persons. My question is , why we have included that one cv can have may persons.
No comments:
Post a Comment