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 > The difference between composite and weak entities?

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 03-21-08, 23:19
partone partone is offline
Registered User
 
Join Date: Mar 2008
Posts: 1
Question The difference between composite and weak entities?

Hi,

A Composite entity can be made out of two Primary Keys (PK) of two different entities. Therefore it can be called as a link table. Therefore the composite entity depends upon the other two entites. Therefore the composite entity is a exsitence dependent on the other two entities.

Therefore do every composite is a weak entity?

TY
Reply With Quote
  #2 (permalink)  
Old 03-22-08, 08:32
r937 r937 is offline
SQL Consultant
 
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,524
that sounds right to me

__________________
r937.com | rudy.ca
please visit Simply SQL and buy my book
Reply With Quote
  #3 (permalink)  
Old 03-22-08, 09:52
Pat Phelan Pat Phelan is offline
Resident Curmudgeon
 
Join Date: Feb 2004
Location: In front of the computer
Posts: 12,605
This reminds me of one of my favorite sayings: In theory, theory and practice are identical. In practice, theory and practice are unrelated.

In all normal cases, a composite entity must be a weak entity because it depends on the two entities that it links.

There are a few cases (all the ones that I can think of are governmental) that can be exceptions to this rule. There is some debate as to whether or not these can even be modeled as weak entities.

One example would be a Louisiana tax purchase, where the taxes have not been paid on a property for too long and the property is put on the tax auction. Because of the way that Louisiana law works, the "purchase" is presumed and actually almost completely processed before the auction occurs, so the buyer is unknown at that point. Once the sale occurs, then the property identifier, the buyer, and the date become a natural candidate key, but they aren't even a candidate key until then because the buyer is unknown.

For all of the cases that a data modeling class would cover, a composite entity is a weak entity. In practice, there are (arguably) a tiny number of exceptions.

-PatP
Reply With Quote
Reply

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