blocks|key|2026051|text|这是我的两点意见：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2026052|我会对不同的应用程序使用不同的数据库，而不是在一个应用程序中使用不同种类的数据。|2026053|你想在同一个应用程序中显示船只和汽车吗？同一战线？您是否曾经执行过同时返回汽车和船的SQL查询？|2026054|或者你基本上把船和汽车当作完全不同的网站？如果它们是完全独立的，并且可以单独支持，并且可以单独修改应用程序，那么使用单独的数据库是有意义的。|2026055|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|$]]

Just my two cents:

I would use separate databases for separate apps, not for separate kinds of data within one app.

Do you want to show boats and cars in the same app? On the same page? Do you ever do an SQL query that should return both cars and boats?

Or are you basically treating boats and cars as completely separate web sites? If they are completely separate, and could be supported separately, and could have the app modified separately, then it makes sense to use separate databases.

blocks|key|5811269|text|浮现在脑海中的一个考虑因素是站点代码的可重用性。在数百个类别中控制单独的数据库用户名:密码组合听起来很烦人。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5811270|在性能方面，我认为分离变得无关紧要，除非您的独立数据库位于不同的机器上。|5811271|也取决于你的使用。|5811272|从长远来看，将它们保存在一个数据库中可能会给你提供更多的灵活性和机会来生成趋势数据或交叉链接类别。|5811273|但是，如果你正在制造一个引擎来销售给特定行业的其他公司，那么每个垂直行业1分贝是有意义的。|5811274|我自己的倾向是情况B，除非特定的需要告诉我另一种情况。|5811275|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

A consideration that springs to mind is re-usability of site code. Controlling separate db username:password combinations across hundreds of categories sounds annoying.

Performance-wise, I think the separation becomes irrelevant unless your separate databases are on separate machines. 

Also depends on your use...

Long-term, keeping them in one db probably gives you more flexibility and opportunity to generate trend data, or cross-link categories.

But, if you are making an engine to sell to other companies in specific industries, then 1 db per vertical makes sense.

My own inclination would be case B, unless a specific need told me otherwise.

blocks|key|2026132|text|只要数据库在同一服务器上的同一用户下，您仍然可以执行连接等操作。但是只有当你的站点的一个部分需要30个以上的表格时，我才会推荐这个方法。当您必须直接在数据库中工作时，它使管理变得容易。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2026133|但是如果你的网站不需要这样的复杂程度，我会建议你不要这么做，这不值得麻烦。|2026134|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

As long as the databases are on the same server under the same user, you can still do joins and such. But i’d only recommend this if you need more than 30 tables for one section of your site.
It keeps management easy when you have to work directly in the database.

But if your site doesnt require such an level of complexity, I would advice against it, its not worth the trouble.

blocks|key|4342649|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4342650|是MySQL、Oracle还是Postgres有关系吗？|blockquote|4342651|4342652|4342653|绝对一点儿没错。|4342654|术语“数据库”在Oracle中的含义与大多数其他数据库中的完全不同。如果在MySQL或Postgres+(或SQL+Server)中考虑的是“数据库”，那么在Oracle中通常会考虑“模式”(=用户)。|4342655|在PostgreSQL中，您不能进行跨数据库查询。因此，对于分离，模式可能更好(因为它更灵活)。|4342656|关于您的实际设计决策:听起来您可能希望将所有内容都放在一个数据库/模式中，但没有足够的信息来真正回答这个问题。|4342657|我认为wegjprgm的回答非常明确。|4342658|entityMap^0|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|R|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|S|7|@]|8|@]|9|$]]|$1|D|3|-4|4|5|6|T|7|@]|8|@]|9|$]]|$1|E|3|-4|4|5|6|U|7|@]|8|@]|9|$]]|$1|F|3|G|4|5|6|V|7|@]|8|@]|9|$]]|$1|H|3|I|4|5|6|W|7|@]|8|@]|9|$]]|$1|J|3|K|4|5|6|X|7|@]|8|@]|9|$]]|$1|L|3|M|4|5|6|Y|7|@]|8|@]|9|$]]|$1|N|3|O|4|5|6|Z|7|@]|8|@]|9|$]]|$1|P|3|-4|4|5|6|10|7|@]|8|@]|9|$]]]|Q|$]]

<blockquote>
 Does it matter if it's MySQL, Oracle or Postgres?
</blockquote>

Absolutely.

The term "database" in Oracle means something completely different than in most other databases. If you are thinking "database" in MySQL or Postgres (or SQL Server) you would normally think "schema" (=user) in Oracle. 

In PostgreSQL you are not able to do cross-database queries. So for separation, schemas are probably better (because it's more flexible).

Regarding your the actual design decision: It sounds like you probably want to have everything in one database/schema but there is not enough information to really answer that. 

wegjprgm's answer pretty much nails it down I think.

Question is this:

Should we have 1 database per vertical or 1 database for everything? Site will contain several for sale ads.

A) 1 db per vertical example
Meaning, when you view these pages:
<a href="http://www.site.com/cars" rel="nofollow">http://www.site.com/cars</a>
http://www.site.com/boats

/cars literally connects to a database lets say "db_cars" and that database ONLY has car data, nothing else in it.
/boats literally connects to a database lets say "db_boats" and that database ONLY has boat data, nothing else in it.

Both databases have the same structure, table names "item" "seller" etc

OR

B) 1 db for everything example
/cars connects to "db_everything" and filters cars based on a table linked to the items table, so WHERE item_type="cars"
/boats connects to "db_everything" and filters cars based on a table linked to the items table, so WHERE item_type="boats"

So would you pick A or B? Any pros/cons to either? Does it matter if it's MySQL, Oracle or Postgres?

One database structure with many databases, or one global database?

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

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

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

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

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

问题是：我们应该为每个垂直领域配备一个数据库，还是应该为所有产品配备一个数据库？网站将包含几个出售广告。A)每个垂直方向1db的示例意味着，当您查看这些页面时： /cars从字面上连接到一个数据库，比方说"db_cars“，这个数据库只有汽车数据，没有其他数据。/boats从字面上连接到一个数据库，比方说"db_boa...

问一个包含多个数据库的数据库结构，还是一个全局数据库？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问一个包含多个数据库的数据库结构，还是一个全局数据库？EN