
For each part of this problem you will need to construct a single SQL query which will check whether a certain condition holds on a specific instance of a relation, in the following way: your query should return an empty result if and only if the condition holds on the instance. (If the condition doesn’t hold, your query should return something non-empty).
Note our language here: the conditions that we specify cannot be proved to hold in general without knowing the externally-defined functional dependencies; so what we mean is, check whether they could hold in general for the relation, given a specific set of tuples.
You may assume that there will be no NULL values in the tables, and you may assume that the relations are sets rather than multisets, but otherwise your query should work for general in- stances.
-
A is a superkey for a relation T (A, B, C, D).
-
The combinations of two attributes in the relation T (A, B, C, D) are each keys.
-
A tuple-generating dependency(TGD)between two relations A and B, having some shared attributes X1, ..., Xn, holds if, for every tuple tA in A, there is some tuple tB in B such that tA[Xi] = tB[Xi] for i = 1,...n.
In other words, for every distinct tuple in A, there must exist a corresponding tuple in B, which has the same values of shared attributes.
Consider three tables Sailors(sid, sname, rating, age), Reserves(sid, bid, sname, bname, date) and Boats(bid, bname, color); Check for a TGD between Sailors and Reserves.
-
A multivalued dependency (MVD) is defined as follows: let R be a schema i.e. a set of attributes, and consider two sets of attributes X ⊆ R and Y ⊆ R.
We say that a multivalued dependency (MVD), written: X ? Y , holds on R if whenever there are two tuples t1, t2 such that t1[X] = t2[X], there also exists a third tuple t3 such that:
• t3[X] = t1[X] = t2[X] • t3[Y]=t1[Y]
• t3[R \Y]=t2[R \Y]Note that R \Y is all the attributes in R that are not in Y , and that t3 need not be distinct from t1 or t2. Note especially that an MVD holds on an entire relation, meaning that any two tuples (in any order) in the relation should satisfy the above conditions if the MVD holds.
To simply the problem, we assume R = {A, B, C, D, E}, X = {A, B, C}, Y = {C, D, E}. Hints: You need self-joins, nested SQL queries and Not Exist or Exists.
• At least 5 tuples for each table.
• One table satisfies the requirement.
• One table fails the requirement.
• For Q2, you will need four tables to test two different combinations.
• For Q3, you will need four tables.

Trending nowThis is a popular solution!
Step by stepSolved in 2 steps

- Consider the following database instance. Table name: Students Primary key: sid Sid sname 7 Ricky 2 Ellen 6 MaryLou 4 Ellen Table name: Courses Primary key: cid cid cname 1 ICS 2 Finance Table name: Register Primary key: sid,cid Foreign key: sid references Students(sid) Foreign key: cid references Courses(cid) sid cid 7 2 2 2 7 1 4 1 5.1) For each of the following statements, show whether the statement is correctly executed or not (assume that the statements are executed in order, which means that if a statement is correctly executed, its effect is reflected in the following statement). If you say the statement is not executed, explain why. INSERT INTO Students VALUES (3, ‘Ellen’); INSERT INTO Students VALUES (6, ‘Ellen’); INSERT INTO Register VALUES (1, 2); INSERT INTO Courses VALUES (5, ‘Systems’); INSERT INTO Register VALUES (6, 5); INSERT INTO Register…arrow_forwardIt is possible to construct a connection such as sec course from a group of relationships that are many to one. Does the relation's many-to-one cardinality restriction get enforced by the main and foreign key constraints? Why do you think that is?arrow_forwardRead Scnerio carefully : Make a Propose and optimal database design in RDBMS for a super store. In which clients came and can purchase products according to their likes and dislikes. Super store have same products of different companies. In the end client received a receipt of their purchase from counter he/she go for bill. Database also save records of stock according to FIFO system. Required to define Entities and their attributes Attributes Types Each Attribute Required Define keys of each entity Define relationship between the entities.arrow_forward
- Question 20 Please fill in the blank correctly.arrow_forwardit says relation hotel already existarrow_forwardSuppose that A and B are two sets of entities connected by a relation R that has multiple one-to-one occurrences (see Figure 1). Think about a scenario in which R's generated connection is coupled with A's. SQL allows null values for attributes that are a part of a foreign key constraint. Give an example of how non-null constraints may be used in SQL to place a restriction on how much A can be involved in R.arrow_forward
- Computer Networking: A Top-Down Approach (7th Edi...Computer EngineeringISBN:9780133594140Author:James Kurose, Keith RossPublisher:PEARSONComputer Organization and Design MIPS Edition, Fi...Computer EngineeringISBN:9780124077263Author:David A. Patterson, John L. HennessyPublisher:Elsevier ScienceNetwork+ Guide to Networks (MindTap Course List)Computer EngineeringISBN:9781337569330Author:Jill West, Tamara Dean, Jean AndrewsPublisher:Cengage Learning
- Concepts of Database ManagementComputer EngineeringISBN:9781337093422Author:Joy L. Starks, Philip J. Pratt, Mary Z. LastPublisher:Cengage LearningPrelude to ProgrammingComputer EngineeringISBN:9780133750423Author:VENIT, StewartPublisher:Pearson EducationSc Business Data Communications and Networking, T...Computer EngineeringISBN:9781119368830Author:FITZGERALDPublisher:WILEY





