blocks|key|3887544|text|只要你的列都不是多值的(例如，一个员工可以有多个部门)，那么你的设计就是最优的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3887545|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

as long as none of your columns are multi-valued (eg, an employee can have multiple departments) then your design is optimal.

blocks|key|1571996|text|您的第一个解决方案更好，第1项到第6项应该都在同一个表users中。如果您有关于部门的更多信息要存储，则需要有一个特定的表departments，该表至少有两列：id和name，然后在users表中，您将有一个department_id列，该列将存储与departments表中的部门相对应的id。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1571997|如果没有存储有关部门的任何其他信息，最好直接将部门名称存储在users表中，以避免每次检索或更新有关用户的信息时都必须连接表。|1571998|entityMap^0|R|5|1P|B|29|2|2C|4|2K|5|2X|A|3I|B|0|U|5|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Y|8|@$9|Z|A|10|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|11|8|@]|D|@]|E|$]]]|I|$]]

Your first solution is better, Items 1 to 6 should all be in a same table <code>users</code>.
If you have more info on the department to store then you need to have a specific table <code>departments</code> which will have at least two columns : <code>id</code> and <code>name</code> and then in the <code>users</code> table you will have a <code>department</code>_id column that will store an id corresponding to a department in the <code>departments</code> table.

If you don't store any other info about the department, it might be better to store directly the department name in your <code>users</code> table to avoid having to JOIN tables everytime you retrieve or update information about a user.

blocks|key|3887550|text|User_Master
------------------

UserID+-+Primary+Key
DeptID++-+Foreign+Key
FirstName
LastName
EmailID
PhoneNumber
FaxNumber


Dept_Master
----------------

DeptID+-+PrimaryKey
DepartmentName|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|3887551|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>User_Master
------------------

UserID - Primary Key
DeptID - Foreign Key
FirstName
LastName
EmailID
PhoneNumber
FaxNumber


Dept_Master
----------------

DeptID - PrimaryKey
DepartmentName
</code></pre>

blocks|key|3887597|text|进一步的思考..。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3887598|别忘了考虑时间。员工可以更换部门吗?您是否有兴趣了解这段历史？如果是这样的话，您将不得不有一个单独的Departments表，并且可能是一个包含EmployeeID、DepartmentID、StartDate和EndDate的服务(或其他)表。|3887599|在考虑随着时间的推移而发生的变化时，电话、传真号码和电子邮件地址是否适合员工或职位？如果珍妮特在财务部得到了主管的工作，她是在新办公室得到一个不同的电话号码，还是电话号码随人而动的地方之一。电子邮件也是如此。地址是hr.officer@example.com还是joe.smith@example.com？如果是前一种情况，在这两种情况下，你可能想要考虑一个位置表，它可以跟踪电话/传真/电子邮件(以及工资等级、FT或PT等)，它有一个DepartmentID外键。|3887600|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Some further thoughts...

Don't forget to think about time. Can employees change departments, and are you interested in knowing this history? If that's the case you'll have to have a separate Departments table, and probably a Service (or something) table with EmployeeID, DepartmentID, StartDate and EndDate.

While thinking about changes that happen over time, do phone &amp; fax numbers and email addresses fit with the employee or the position? If Janet in accounts lands the supervisor's job, does she get a different phone number in her new office, or is it one of those places where the telephone numbers move with the people. Ditto for email. Are addresses hr.officer@example.com or joe.smith@example.com? If the former in both cases you probably want to think about a Position table that keeps track of phone/fax/email (as well as paygrade, FT or PT etc) which has a DepartmentID foreign key.

blocks|key|1572090|text|如果您正在使用SQL进行思考，那么您最好(至少)使用第一范式进行思考。多值列不仅速度慢，而且是迈向混乱的第一步。如果您转向基于Nosql的解决方案，则此规则不适用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1572091|普通的表单2到5有助于填充表，但对您的web客户端没有帮助。从完全规范化中获得的最大好处是保证数据库不会自相矛盾。例如，同一部门在两个不同的员工记录(行)中有两个不同的名称。|1572092|你需要添加到你的愿景中的最重要的东西是视图。你可以使用视图来达到很好的效果，让data+lok更像你想要的网页外观。这将使构建web客户端变得更加容易。在某些领域，视图也不会有帮助。|1572093|采用下拉列表。如果正如所建议的那样，人们可以有多个电话号码，您可能希望在员工页面上有一个电话号码下拉列表。这基本上是一个多值字段，视图在这方面没有特别的帮助。|1572094|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|$]]

If you are thinking in SQL, you definitely do well to think in (at least) first normal form. Multivalued columns are not only slow, they are also the first step towards chaos. This rule doesn't apply if you move towards a Nosql based solution.

Normal forms 2 through 5 help with populating the tables, but won't help you with your web client. The biggest thing you'll gain from full normalization is the guarantee that the database doesn't contradict itself. Things like two different names for the same department, in two different employee records (rows).

The big thing you need to add to your vision is views. You can use views to very good effect to make the data lok more the way you want a web page to look. This will make building the web client lots easier. There are areas where views aren't going to help either.

Take drop down lists. If as has been suggested, people can have more than one phone number, you might want to have a drop down list for phone numbers on the employee's page. This is basically a multivalued field, and views aren't especially helpful in that regard.

blocks|key|5355516|text|我认为您可以使用department1、department2等部门列，它们将包含每个部门的ids。您可以创建另一个名为department的表，该表将包含ids和部门名称。现在，您可以将第一个表中的部门ids链接到第二个表。如果一个员工属于多个部门，这不会造成混乱。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5355517|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I think you can have department columns like department1, department2 etc. which will consist ids of each department. You can create another table called department which will have ids and department name. Now you can link the department ids in the first table to the second one.
This will not mess if an employee is belonging to multiple departments.

I'm a newbie messing around at designing a database. I want to create a database(using mysql) that contains employee information. Then I will write Web Client to display each employee profile. I so far the columns would be:

<pre><code>1) user id
2) first name
3) last name
4) email address
5) phone number
6) fax number
7) department(which will be like a category)
</code></pre>

Would the best design be make items 1-6 columns in one table and then have the department column in it's own table(with a id column)? 
Or should I make all the items their own table, giving each table an extra id column....and would this be #1 normalization form?

Database Design - Which would be best for this?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我是个设计数据库的新手。我想创建一个包含员工信息的数据库(使用mysql)。然后，我将编写Web客户端来显示每个员工的个人资料。到目前为止，我的专栏是：1) user id2) first name3) last name4) email address5) phone number6) fax number7) department(which will be like a category)最

问数据库设计--哪一个是最好的？
EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库设计--哪一个是最好的？EN

回答 6

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问数据库设计--哪一个是最好的？
EN