Is this okay to have two foreign keys in one table referencing one primary key of other table?
EmployeeID is a primary key in the employee table and appearing as a foreign key twice in the timesheet table.
There will be few admin users filling up timsheets on the behalf of other employees.
In the timsheet table field 'TimsheetFor' will have employeeID of that person who has worked on projects and field 'EnteredBy' or 'FilledBy' will have employeeid of that person who has filled up this timesheet.
Which of the following option is correct?
NOTE: Tables are showing only those fields which are related to this question.
Yes, it is okay to have two fk to the same pk in one table.
In scenarios where a table can have relationships with multiple other tables, you will need to add multiple foreign keys to a table. For the Employee table, you need to add foreign keys that reference the primary keys of the Department table and the Insurance table.
That's impossible. A FOREIGN KEY constraint can only point to one table and each table can only have one PRIMARY KEY constraint.
If you mean "can foreign key 'refer' to a primary key in the same table?", the answer is a firm yes as some replied.
I would go with option 1. It is perfectly fine to have two foreign key columns referencing the same primary key column in a different table since each foreign key value will reference a different record in the related table.
I'm sure option 2 would work, but you would essentially have a 1-to-1 relationship between TIMESHEET_TABLE
and TIMESHEET_FILLED_BY
, making two tables unnecessary and more difficult to maintain.
In fact, if both ENTERED_BY
and TIMESHEET_FOR
are required in pairs, using option 1 makes far more sense because this is automatically enforced by the database and foreign keys.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With