If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

 
Go Back  dBforums > General > Database Concepts & Design > Normalization with no functional dependencies

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 11-15-11, 01:40
chrisparton1991 chrisparton1991 is offline
Registered User
 
Join Date: Nov 2011
Posts: 2
Question Normalization with no functional dependencies

Hey guys,

I'm currently doing a databases subject at university and I'm studying for my exam. I've been looking through past exams (which all feature a decent amount of normalization), and I'm stuck on one of the questions.

The question simply asks me to find the highest normal form of a schema - no actual normalization is required.

The schema is called Transaction and it has three attributes: buyerId, ownerId and propertyId. The schema contains no functional dependencies.

Because the schema contains no functional dependencies, would you say that it doesn't have a primary key, and therefore does not satisfy 1NF, or could it be said that the primary key is a composite key that is composed of all the attributes (which satisfies 1NF)?

In the latter case, it would satisfy 2NF as there are no partial dependencies, and it would satisfy 3NF as there are no transitive dependencies. The determinant is a candidate key (you can't remove any attributes from it), so the schema would seem to be in (at least) BCNF.

What are your thoughts? Am I going about this in the wrong way?

Thanks in advance,
Chris
Reply With Quote
  #2 (permalink)  
Old 11-15-11, 15:24
futurity futurity is offline
Registered User
 
Join Date: May 2008
Posts: 270
Quote:
Originally Posted by chrisparton1991 View Post
Because the schema contains no functional dependencies, would you say that it doesn't have a primary key, and therefore does not satisfy 1NF
No. Think of your most basic many-to-many intersection table, or your most basic lookup table. Do they have any functional dependencies? Do they have a primary key?

Quote:
or could it be said that the primary key is a composite key that is composed of all the attributes (which satisfies 1NF)?

In the latter case, it would satisfy 2NF as there are no partial dependencies, and it would satisfy 3NF as there are no transitive dependencies. The determinant is a candidate key (you can't remove any attributes from it), so the schema would seem to be in (at least) BCNF.
This is the right direction. Not sure which normal forms you've all covered, but if you go through their definitions, like you have here, then you shouldn't have any problems arriving at the correct answer.
Reply With Quote
  #3 (permalink)  
Old 11-16-11, 07:39
chrisparton1991 chrisparton1991 is offline
Registered User
 
Join Date: Nov 2011
Posts: 2
Thanks for the quick reply. I had a feeling it wouldn't be as simple as "it doesn't satisfy 1NF."

We've covered up to 5NF in lectures, but the lecturer only expects us to decompose until we arrive at BCNF, so I can stop there.

Cheers,
Chris
Reply With Quote
Reply

Tags
bcnf, dependency, design, functional, normalization

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On