I'm working on a recruiting web site and I was wondering what would be best between:
1) A User table, the employer accounts are linked to a company (therefore when companyID is null then it's a job seeker) 2) 2 complete separate tables one for job seekers, one for employers. That way on the long run, it's possible to optimize queries a bit more if it becomes hugely successful.
Both approach have pros and cons:
With 1) it would be possible for exemple to create only one login form which would handle both job seekers and employers.
The data is the same but the entity is different.
I have mixed feelings. What do you think?