I have a table called operators. Each operator (operatorID) will have employees but the number will vary from 1 to n. So, my thinking is that I should create an employees table that includes all employees for all operators, using a compound key including operatorID and employeeID. Is that correct?
Is there reason (if it's not a business rule) that one wouldn't want to lump all employees?
Am I right in thinking that primary keys are often constituted by tuples? In forestry, a standID value would commonly reference any number of attributes (dominant species, some structural trait, management objective, etc.). Is that fairly common?