Consider the following relational database schema that contains information about employees and projects to which they are assigned. Emp (eid, lastname, gender, DOB) Assign (eid, pid, hours) Proj (pid, pname, budget, manager_eid) Answer the following questions. (a) Find two superkeys in the Proj table — both of these two superkeys should NOT be same as the primary key. You should use appropriate set notation if the superkey contains multiple attributes. (b) Suppose the Emp and Proj tables have been created appropriately. Define (i.e., create) the Assign table in SQL (Just create only one table.) You should follow all the requirements discussed in the class. (c) Suppose in the Proj table a project has changed pid from P06 to P07. From the perspective of integrity constraints, how should this modification be handled?
Consider the following relational
Emp (eid, lastname, gender, DOB)
Assign (eid, pid, hours)
Proj (pid, pname, budget, manager_eid)
Answer the following questions.
(a) Find two superkeys in the Proj table — both of these two superkeys should NOT be same as the primary key. You should use appropriate set notation if the superkey contains multiple attributes.
(b) Suppose the Emp and Proj tables have been created appropriately. Define (i.e., create) the Assign table in SQL (Just create only one table.) You should follow all the requirements discussed in the class.
(c) Suppose in the Proj table a project has changed pid from P06 to P07. From the perspective of integrity constraints, how should this modification be handled?
Trending now
This is a popular solution!
Step by step
Solved in 3 steps
