Redundant info in new table?

Friday, July 11, 2014

A TASK is linked to a TASK_ROLE that associates parties + roles to a specific TASK. I need another table, TASK_RATE, that stores the rate of every party that participoates in a specific TASK. I could get those associations with a FK to TASK_ROLE, but the problem is that a party can have more than one role and can be listed more than once.



TASK:
PKIDTASK
1
2
3

TASK_ROLE:
PKIDTASK_ROLE | IDTASK | IDPARTY | IDROLE
1 1 8 3
2 1 8 2
3 1 5 2
4 1 4 2


I tought about creating the table like this



TASK_RATE:
PKIDTASK_RATE | IDTASK | IDPARTY
1 1 8
2 1 5
3 1 4


IDTASK + IDPARTY are unique, unlike in TASK_ROLE. But wouldn't be this redundant info since PARTY-TASK associations are already defined in TASK_ROLE?


How do I solve this?







http://ift.tt/VTUQrF