|
|
I have 3 main user for a system; admin, company, and student. Each user will have their own login ID and password. I would like to know which of the following is the best approach in designing the database for all 3 users:
1) create a login table for all 3 user; student login, admin login, and company login. This approach have to test from table to table to find the actual record.
2) create one login table for all user with few check column to verify whether this user is admin, student or company. This approach may take up a lot of hdd spaces.
These are the 2 idea I have in mind. So which is the proffessional way to design the actual database in real life environment? Or is there any better approach?
Thanks all!
|
|
|
|
|
|
|
|
|
|
|
|
swspm
