I'm developing a database where I will have two types of users: Employee and Client. I'm thinking it would be ideal to just have one big
USERS TABLE with a
user_ID as PK and
Type column to distinguish whether the user is an
Employee or a
Client. This is to make it more convenient when a user logs-in where it will only check one table:
USERS TABLE for
However, I realized that this means I would be losing the opportunity to have separate ID's as PK for Employees and Clients (
Would having another table called
EMPLOYEE TABLE and
CLIENT TABLE (that have
user_ID_FK as FK,
client_ID respectively) be ideal or would that de-normalize the tables?
How best to handle user log-in where there are multiple different types of users (Employee, Client, etc.)?