数据库设计：3种类型的用户，单独还是一个表？ [英] Database design: 3 types of users, separate or one table?

问题描述

我有3种类型的用户：

• 管理员


• 供应商


• 员工

每个用户类型都有不同的用户界面并可访问不同类型的数据。他们唯一的相似是他们使用一个Web应用程序，但他们访问完全不同的东西。最好将它们全部放在一个用户表中，例如tbl_users，或者最好创建tbl_admins，tbl_suppliers，tbl_employees？

Each user type will have different user interface and access different types of data. Their only similarity is they are using one web application but they access totally different things. Is it better to put them all in one user table like tbl_users or is it better to create tbl_admins, tbl_suppliers, tbl_employees?

推荐答案

在设计表格时需要考虑的不一定是他们将要访问的内容，以及类似/不相似的内容，而是用户级别本身是否相似/不相似。

What you need to consider when designing tables is not necessarily what they'll have access to and how that is similar/dissimilar, but rather how the user levels themselves are similar/dissimilar.

例如，如果用户类型具有相同的属性（名称，电子邮件，出生日期等），则它们属于一个表格，并且表示其权限级别。

For example, if the user types will have the same attributes (name, email, birthdate, etc), then they belong in one table together with a column indicating their privilege level.

这也有助于更改用户的权限级别，例如，通过更新用户表中的记录，您可以将普通员工变为管理员。

This also facilitates changing privilege levels for a user, whereby you can make an ordinary Employee into an Admin, for example, by just updating the record in the user table.

如果供应商是具有不同属性的不同类型的对象，供应商可能属于自己的表。

If Suppliers are a different type of object with different attributes than the other two, Suppliers may belong in their own table.

或者，还有一件事要考虑：您可以使用一个 users 表，该表仅保存有关所有三种类型的用户的非常有限的信息，如果类型的扩展属性彼此之间没有良好关联，您可以将其他表中的外键存储到主用户表。

Or, one more thing to consider: You might use a users table that holds only very limited information about users of all three types, and if the types have extended attributes that don't relate well to one another, you can store those in other tables with a foreign key back to the main users table.

这篇关于数据库设计：3种类型的用户，单独还是一个表？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！