yea or nay - Allowing nulls on a FK column
-
My personal opinion would be to use a linking table to hold the employeeID and projectID. This way if an employee doesn't have a project, then there simply wouldn't be a record in that table with their ID.
Just my two cents...
______________________________________________________________________
Personal Motto: Why push the envelope when you can just open it?
If you follow the direction given HERE[/url] you'll likely increase the number and quality of responses you get to your question.
Jason L. Selburg -
Agreed. This has additional benefit if the relationship ends up being a many-2-many...ie if over time an employee can work on more than 1 project for this then you just add in a start + end date/time, to track a history of same.
Current design only allows tracking of 1 current project.
-
Thanks guys! That does help clear it up. I was not in favor of using that approach (i.e. allow nulls) but my co-worker was very much for it. So I told him I would post the question, in a non-partisan format - which I think I did
Hopefully he will see the light. Thanks again.
Viewing 3 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply