Re: Functional dependencies

From: shannon <shannon_at_nolunchmeat.com>
Date: Mon, 05 Jan 2004 23:33:14 +0100
Message-ID: <btcom2$6kv$01$1_at_news.t-online.com>


You are right Bob,

i meant to teach him how to fish,

instead I have handed him a fish, was not my intention..

Bob Badour wrote:

> Shannon,
> 
> Do you do your kids' homework for them too?
> 
> "shannon" <shannon_at_nolunchmeat.com> wrote in message
> news:btbtel$ohd$00$1_at_news.t-online.com...
> 

>>You first need to break this down into to managable Entities,
>>perhaps one each for Equipment, Manafacturer, Buyer, Department as these
>>are real world entities,
>>
>>Each of these entities will possibly have a unique value, (key) For
>>example Equip ID for the 'unit of' equipment.
>>
>>A functional dependency is a constraint between two sets of attributes
>>from the database. From the above suggested Entities and their
>>attributes we could identify the following FDs
>>
>>the Equip ID determines the EquipmentModel
>>
>>the ManufacturerID determines the ManufacturerName
>>
>>the BuyerName determines the BuyerPhone,
>>
>>
>>
>>Burim wrote:
>>
>>
>>>Please can you help me!
>>>In this relation:
>>>
>>>Equipment(EquipID, EquipmentModel, ManufacturerID, ManufacturerName,
>>>DateInstallation, BuyerName, BuyerPhone, DepartmentInstallation,
>>>AddressDepartmentInstallation)
>>>
>>>to show functional dependencies.
>>>
>>>
>>>
>>
>
> Received on Mon Jan 05 2004 - 23:33:14 CET

Original text of this message