原则 2.1 - 将实体映射到多个表
我有以下数据库情况：
wp_users (user table generated by wordpress)
ID | user_login | ...
wp_sp_user (extension to the wp_users table)
ID (FK) | surname | address | ...
现在我已经尝试了几个小时将这两个表“融合”到一个 User 实体中，例如：
class User {
var ID;
var user_login;
var surname;
var address;
...
}
有什么方法可以在不修改wp_user 表（由于更新原因我不想这样做）？
I have the following database situation:
wp_users (user table generated by wordpress)
ID | user_login | ...
wp_sp_user (extension to the wp_users table)
ID (FK) | surname | address | ...
Now I've already been trying for hours to "fuse" those two tables into one single User entity, e.g:
class User {
var ID;
var user_login;
var surname;
var address;
...
}
Is there any way to accomplish such a mapping without modifying the wp_user table (which I don't want to do for updating reasons)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
有时数据库重构是不可能的，或者表有自己的“存在理由”。在这种情况下，您可以使用继承。您的 User 类可以扩展 Account。将帐户映射到 wp_users 并使用 wp_sp_user 表对其进行扩展。用户类将使用两个表的列。
以下是学说文档：
https： //www.doctrine-project.org/projects/doctrine-orm/en/current/reference/inheritance-mapping.html
Some times database refactoring is not possible or the table has his own "raison d'être". In this cases you can use inheritance. Your User class can extens Account. Map Account to wp_users and extend it with wp_sp_user table. User class will use columns of the two tables.
Here is the doctrine documentation:
https://www.doctrine-project.org/projects/doctrine-orm/en/current/reference/inheritance-mapping.html
这是不可能的。这样做也是没有意义的。
您需要在 MySQL 中将表物理合并在一起，并为该表创建一个 Doctrine 实体。这是确保数据干净且完全规范化的唯一方法。
另一种可能的解决方案是为每个表创建一个实体，并使用业务对象来组合每个表的结果。这根本不是一个很好的解决方案，因为您必须处理应用程序层上的约束，并且您启动的查询量将增加一倍。
This is not possible. It also doesn't make sense to do so.
You will need to physically merge the tables together in MySQL and create a Doctrine entity for that table. This is the only way you can ensure your data is clean and fully normalized.
Another possible solution is to create one entity for each table and use a business object to combine results from each. This is not a very nice solution at all, as you will have to handle constraints on the application layer, and you will double the amount of queries you launch.