blocks|key|3904574|text|下一类用户-添加另一个表-会发生什么？最好不要。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3904575|您可以添加一个名为type的新列或类似的列。一种方法是它包含一个指示类型的数字，例如|offset|length|style|CODE|3904576|1+=+normal+user
2+=+admin
3+=+banned|code-block|syntax|javascript|3904577|或者，您甚至可以添加另一个名为user_types的表来引用它，但只有在类型随时间变化的情况下才需要这样做。|3904578|如果您需要组合类型-用户同时具有多个类型，那么您可以将该列设置为位字段。|3904579|什么时候需要单独的桌子？|3904580|当这些不同的用户将具有不同的属性并且每种类型的用户的表将不同时。|3904581|entityMap^0|0|9|4|0|0|F|A|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@$D|Y|E|Z|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|10|8|@]|9|@]|A|$K|L]]|$1|M|3|N|5|6|7|11|8|@$D|12|E|13|F|G]]|9|@]|A|$]]|$1|O|3|P|5|6|7|14|8|@]|9|@]|A|$]]|$1|Q|3|R|5|6|7|15|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

What happens with the next type of users - add another table? Better not.
You could add a new column called <code>type</code> or something like that. One way would be it containing a number indicating the type like
<pre><code>1 = normal user
2 = admin
3 = banned
</code></pre>
or you could even add another table called <code>user_types</code> that refer to it, but that would only be necessary if you have the types changing over time.
If you need to combine types - users having multiple types at once, then you could make the column a bit field.
<h3>When do you need seperate tables?</h3>
When these different users would have different attributes and the tables for each type of users would differ.

blocks|key|4043495|text|满足多种标准的可扩展解决方案如下所示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4043496|包含用户数据的角色表，包含角色的users|offset|length|style|CODE|4043497|table+-连接两者的roles|unordered-list-item|4043498|
|4043499|junction表，user2roles|4043500|4043501|你将用户数据与他们在应用程序中的实际角色分开-每个用户至少会有姓名和姓氏，这些与他们的权限或角色无关。|4043502|您很可能需要添加更多角色。例如，一个角色是admin。另一个角色正在被禁止。另一个角色可以被禁止一周，两周等等-基本上你可以在你去的时候添加这些角色，而不需要改变你的表来支持未来的功能。|4043503|您的应用程序(php、python等)收集数据，然后对这些角色执行操作。|4043504|现在你有了一个已经建立了关系的系统，你可以扩展，这很容易被幼儿园的孩子们理解。|4043505|这是一个混合了权限和角色的简化系统，您可以进一步扩展它，但最好保持简单。|4043506|entityMap^0|0|G|5|0|C|5|0|0|A|A|0|0|0|L|5|0|0|0|0^^$0|@$1|2|3|4|5|6|7|11|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|12|8|@$D|13|E|14|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|15|8|@$D|16|E|17|F|G]]|9|@]|A|$]]|$1|K|3|L|5|6|7|18|8|@]|9|@]|A|$]]|$1|M|3|N|5|J|7|19|8|@$D|1A|E|1B|F|G]]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@]|9|@]|A|$]]|$1|R|3|S|5|6|7|1E|8|@$D|1F|E|1G|F|G]]|9|@]|A|$]]|$1|T|3|U|5|6|7|1H|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1I|8|@]|9|@]|A|$]]|$1|X|3|Y|5|6|7|1J|8|@]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|10|$]]

The scalable solution that satisfies multitude of criteria would be this:

<ul>
<li>table that contains user data, <code>users</code></li>
<li>table that contains roles - <code>roles</code></li>
<li>junction table that connects the two, <code>user2roles</code></li>
</ul>

You keep the user data separate from their actual role in your app - every user will at least have name and last name, those are not related to their permissions or roles.

You will most likely need to add more roles. For example, one role is being an <code>admin</code>. Another role is being banned. Another role can be being banned for a week, 2 weeks etc - basically you can add those as you go, without needing to alter your tables to support future functionality.

Your application (php, python, whatever) collects the data and then acts upon those roles.

Now you have a system that's got established relations, that you can scale and that's easy to understand by kids in kindergarden.

This is a simplified system that mixes permissions with roles, you can further expand it but IMO it's better to keep it simple.

blocks|key|584218|text|你需要考虑禁止的概念将如何在现实世界中发挥作用。你只是想要一面旗帜吗？他们是什么时候被禁止的，被谁禁止的呢？过去禁止历史吗？被禁制者的回应机制？投诉列表，包括用户/日期/原因？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|584219|数据模型是系统中最难发展的部分，所以你需要考虑所有可能的未来，甚至是路线图上还没有的东西。|584220|为了提高效率，您可能决定要一个ban表和一个ban列。但这也是要付出代价的，因为你现在在多个地方捕捉到了相同的事实。|584221|这些问题很微妙，有时甚至很复杂。不要接受一刀切的答案。|584222|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|L|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|M|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|I|$]]

You need to think about how the banning concept will play out in the real world. Do you just want a flag? What about when they were banned and by whom? past banning history? a response mechanism for the banned? A list of complaints, with user/date/reason?

Data models are the most difficult part of a system to evolve, so you want to think about all manner of possible futures, even stuff you don't have on the roadmap just yet.

You might decide, for efficiency, that you want a ban table and a banned column. But there's a price to be paid for that too, since you're now capturing the same fact in multiple places.

The issues are subtle and sometimes complex. Don't accept blanket one-size-fits-all answers.

What would be the "correct" way of organizing banned users?

Should I simply add a new column in the existing <code>users</code> table called <code>is_banned</code> that acts as a boolean or should I create a new table called <code>banned_users</code> that acts as a pivot table with the <code>user_id</code>?

The same question goes for administrators. Should I create a new table for site admins or just create a new column called <code>is_admin</code>?

What about performance of the two options?

Thanks.

Separate table for banned users?

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

组织被禁用户的“正确”方式是什么？我是应该简单地在现有的users表中添加一个名为is_banned的新列作为布尔值，还是应该创建一个名为banned_users的新表作为具有user_id的数据透视表同样的问题也适用于管理员。我应该为站点管理员创建一个新表，还是只创建一个名为is_admin的新列这两个选项的性能如何...

问为被禁止的用户单独的表？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问为被禁止的用户单独的表？EN