You're getting into 4NF/5NF territory here. One way to handle the problem is
to create your makeshift table. The Primary Key would be employee_number,
with hours_worked being the other column. Depending on additional business
rules and requirements (such as salary history), you may need to add more
columns and/or tables, or it may just need to be handled programmatically.
Bret A. Murphy <murphybret_at_aol.com> wrote in message
news:19991105145343.04429.00002582_at_ng-fo1.aol.com...
> I am a little confused on the definition of this term. Looking at
example:
>
> employee number > name, telephone, hrs_worked, pay_rate
>
> This is a makeshift table, with employee number being primary key and
non-key
> attritbutes to the right.
>
> This might not be the best example, but assume pay rate is dependent on
> hrs_worked, hence, transitive dependency. But, creating another table with
> hrs_worked as primary key does not make sense, does it?
>
>
> Thank you.
>
>
> Bret A. Murphy
>
>
>
>
>
Received on Fri Nov 05 1999 - 14:17:58 CST
