[英]Database - What is a good database design for a booking system?
I have a school task where I have to build a booking system for meetings for a (fictional) company that has to fulfill the requirements in this pdf: http://docdro.id/FmHngHe (its better for you to read it then me trying to explain the details, all you have to read is part 2 and half of part 3. Its not that much :) ) 我有一项学校任务,必须为(虚构的)公司建立会议的预订系统,该系统必须满足以下pdf中的要求: http : //docdro.id/FmHngHe (最好让您先阅读一下试图解释细节,您只需要阅读第2部分和第3部分的一半即可。
The problem I am facing right now is to create a proper database design for this project. 我现在面临的问题是为该项目创建正确的数据库设计。 I have a vague idea of how the design should look like.
我对设计的外观有一个模糊的想法。 I know for example (approximately) what entity types I should have for this project but I am struggling in trying to figure out how all the tables should be connected.
例如,我(大概)知道该项目应具有的实体类型,但是我在努力弄清楚应该如何连接所有表的努力。 What should the relationships be like and what extra relationship tables do I need.
关系应该是什么样的,我需要什么额外的关系表。
This is what I got so far: 这是我到目前为止所得到的:
But it feels like I am missing a big part of the puzzle here. 但这似乎让我错过了很大一部分难题。 It feels incomplete.
感觉不完整。 I feel like there should be a whole lot more relationship tables in the design but then I will end up with over 10 tables which feels like a bit much for such a small project or am I doing this completely wrong?
我觉得设计中应该有更多的关系表,但是最终我会得到10个以上的表,对于一个如此小的项目,感觉有点太多了,还是我做错了吗?
I would like this to be a very simple design. 我希望这是一个非常简单的设计。 Am I overcomplicating this?
我使这个复杂化了吗?
Please help. 请帮忙。
Thanks! 谢谢!
I would suggest, first of all, write all the requirements in one table. 我建议首先将所有要求写在一张表中。 1 row is the flat structure of all the requirements.
1排是所有要求的平面结构。 Then start breaking it one by one.
然后开始一一破解。 That 1 table structure should be having all the required columns.
该1表结构应具有所有必需的列。 Then follow Normalization concepts of breaking 1 single table into multiple tables.
然后遵循将1张单个表拆分为多个表的规范化概念。
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.