View Single Post
Unread 12-02-2011, 03:57 PM   #9
Jorge
somebody shut me the fark up.
 
Jorge's Avatar
 
Join Date: 01-23-04
Location: DFW, San AntonioTx
Downloads: 0
Uploads: 0
Default

Quote:
Originally Posted by dmprantz View Post
Not to be jerky, but this is not correct. In database terms, a team and a member would each be an entity or table. The table would then have attributes defined in it. One such attribute would be a unique, non-null value, the primary key. Other attributes could be the name of each. Each non-key attribute should depend on the primary key to be normalized at a certain level (3NF). Each entry in the table is called a tuple, and each tuple must have a primary key. Over the years, tuple/attribute have been displaced by record/field, and then again by row/column. Each entity can be associated to another through the use of relations. Relations are generally either defined by a foreign key reference (1:∞) or by a seperate table with foreign keys to each of the related ones (∞:∞).

dmp
Thanks for using your powers for good
__________________
You can't be a real country unless you have a beer and an airline - it helps if you have some kind of a football team, or some nuclear weapons, but at the very least you need a beer. --Frank Zappa

BOOGITY, BOOGITY, BOOGITY!!!

Recipient of a Huggies box!

Shut up, and cook!!!!
Jorge is offline   Reply With Quote