There are none. A functional dependency implies that, after eliminating any duplicates involving both the dependent and determinant columns, you can stick an UNIQUE onto the determinant columns. For instance, UNIQUE(A,B) does not work because a1,b1 appears twice, UNIQUE(A,C) fails because a1,c2 appears twice, and UNIQUE(B,C) fails because b1,c1 appears twice.
Thanks, that clears things up. But in what Normal Form would you say this relation is in? – user1051798 Nov 19 at 13:26.
Functional dependencies hold in/apply to a database DESIGN. They do not "exist in a relation". It could be said of a relation that it SATISFIES some set of functional dependencies, but it is meaningless and confused to say that a functional dependency "exists in a relation".
As Victor more or less pointed out, your example relation satisfies only the trivial FD {ABC} -> {ABC}. As for your other question, "what normal form is this relation in", once again this question is completely meaningless and confused, because the property of "being in some normal form", applies only to a design, not to some particular relation value. In relational terms : only a relation variable can be in some normal form, depending on which FDs are suppposed to hold in it, but a relation value cannot have such a property.So, assuming that you are indeed talking of the declaration of a relation variable with a heading {A B C}, in which there are no nontrivial FDs (i.e.
Only {ABC} -> {ABC} holds), this relation variable is at least in BC normal form. If there are no join dependencies, then your relvar is also in sixth normal form (no that's not a counting error).
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.