我正在开发一个网站，首先将有三个明确的子网站：论坛、新闻和日历。
每个子站点都将拥有自己的数据库，所有这些数据库共有一个用户表，该表需要位于每个数据库中，以便可以完成连接。
如何同步所有用户表，以便无论在哪个数据库中进行更新，所有数据库都将具有相同的用户表。
我不担心是否有短暂的同步延迟（小于 1 分钟），并且我希望解决方案尽可能简单。
I'm developing a website which to begin with will have three clear sub sites: Forum, News and a Calendar.
Each sub site will have it's own database and common to all of these databases will be a user table which needs to be in each database so that joins can be done.
How can I synchronize all the user tables so that it doesn't matter in which database I make an update, all the databases will have the same user table.
I'm not worried if there is a short sync delay (less than 1min) and I would prefer that the solution was a simple as possible.
发布评论
评论（4）
我把问题/解决方案复杂化了。
由于数据库（暂时）存在于同一服务器上，因此我可以使用非常简单的 查看。
I was over complicating the problems/solution.
Since the databases will (for the time being) exist on the same server, I can use a very simple View.
为什么子站点需要有自己的数据库？ 难道不能只使用一个数据库，为每个应用程序使用单独的表吗？ 或者，在 PostgreSQL 中，您可以使用模式达到相同的效果。
Why do the sub-sites need to have their own databases? Can't you just use one database, with separate tables for each of the applications? Or, in PostgreSQL, you could use schemas to the same effect.
尽管我不太赞同这样的架构，联合表 可能会做你想做的事。
Though I would hardly endorse an architecture like this, federated tables may do what you want.
一个应用程序可以登录多个数据库。 虽然我提倡 kquinn 的“全在一个数据库中”的答案，因为如果您确实必须拥有单独的数据库，那么联接将起作用，至少可以从一个数据库访问用户表。 跨多个数据库“克隆”一个表充满了危险，这并不好笑。
A single app can log into more than one database. While I'd advocate kquinn's answer of "all in one DB", becaue joins will work then, if you really must have separate databases, at least have the user table accessed from one database. "Cloning" a table across multiple databases is fraught with so much peril it's not funny.