两个Datacontext之间的关系
我有两个数据库。主数据和产品数据。 我将用户和员工存储在 MasterData 中，并将任务存储在 ProdcutData 中。 任务实体具有用户属性。它显示哪个用户创建了此任务。
如果我只使用一个数据库和一个 DataContext，我可以在两个实体之间定义一种或多种关系。但我必须使用两个数据库和数据上下文。
我是否有任何解决方案可以定义不同数据库、数据上下文中的两个实体之间的关系？
提前致谢：l。
I have two database. MasterData and ProductData.
I store the Users and Employees in the MasterData and I store the Tasks in the ProdcutData.
A Task entity has a User property. It shows which user created this Task.
If I used just one Database and one DataContext I could define a one and more relationship between two entities. But I must use two Databases and datacontexts.
Are any solution that I define relationship between two entities that are in different databases, datacontexts?
thanks advance: l.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这不是一个完整的答案，但它可能会让您想到另一种解决方案。
根据您使用的 DBMS，您也许能够创建从一个数据库到另一个数据库的同义词或可更新视图（或类似的内容）。您的 DataContext 可以包含同义词/视图和表。
在sql服务器中：
http://msdn.microsoft.com/en-us/library/ms177544.aspx
This is not a full blown answer, but it might get you to think of another solution.
Depending on the DBMS you are using, you might be able to create synonyms or updateable views (or something similar) from one database to the other. That you DataContext can contain the synonyms/views and the tables.
In sql-server:
http://msdn.microsoft.com/en-us/library/ms177544.aspx
好吧，除非我错过了一些东西，否则无论是 L2S 还是 EF，都无法连接来自不同上下文/数据库的两个实体。另一种方法是汇集来自两个上下文的所有可能相关的数据，并执行内存中的 linq 来执行关系操作，但这肯定会带来加载过多数据的性能问题。
这是一个“新颖”的想法，为什么不使用DataSet呢？不同的表适配器可以使用不同的连接字符串。它与 L2S/EF 相比相当陈旧，但它会为您提供最多的铃声和信息。关系的口哨声。
我确实有一个问题，如果将用户及其任务保存在单独的数据库中，如何处理引用完整性？
Well, unless I missed something there is no way to join two entities from different contexts/databases regardless if its L2S or EF. Alternative is pooling all possibly relevant data from two contexts and doing in-memory linq to do relational operations, but that certainly poses performance problems of loading too much data.
Here's a "novel" idea, why not use DataSet? Different table adapters can use different connection strings. It is rather archaic next to L2S/EF but it will offer you most bells & whistles of relationships.
I do have one question, if you keep users and their tasks in separate dbs how do you handle ref integrity?
Synonym 是一个很好的解决方案，但 EF 还不支持它......
http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions /suggestions/1052345-support-for-multiple-databases?ref=title
再次感谢！
Synonym is a good solution, but the EF does not support it yet....
http://data.uservoice.com/forums/72025-ado-net-entity-framework-ef-feature-suggestions/suggestions/1052345-support-for-multiple-databases?ref=title
Thanks again!