How to handle necessary duplicate entries
<p>Please help me out with this conundrum. What would be the best practice to overcome the following situation. Consider the following database:</p>

<p><code>ID | Name | HIREDATE | TERMDATE
</code>
<code>01 | John | 01/01/14 | 07/01/14</code></p>

<p>So, john here, as you can see left the company back in july 1st. He is however re-hired at a later date (Say, I dunno, 2/1/15). What would the community do?</p>

<p>a) Duplicate his entry and asign him an entirely different ID? -Possible cons: Might skew statistics when calculating things such as attrition, new hires, etc etc.</p>

<p>b) Add a new column for rehires despite it being a rare occurence and might go largely unused. -Possible cons: Might collide with other functions within the program such as searching for current employees unless checked.</p>

<p>c) Remove term date: out of the question. Statistics need to show all that were hired and termed at any given time and that would render the calculations innacurate.</p>

<p>d) Other: _________ &lt;

<p>I am leaning with option "a". I think there might be a way to adjust for calculations to reflect that there were rehires when calculating attrition and growth. What does the community think?</p>