blocks|key|2127458|text|谷歌是你最好的朋友|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2127459|图的一般定义和解释见这篇文章|unordered-list-item|offset|length|2127460|有关EF和实体图的特定信息，请参见这里|2127461|entityMap|0|LINK|mutability|MUTABLE|url|https://en.wikipedia.org/wiki/Graph_database|1|http://www.entityframeworktutorial.net/EntityFramework5/update-entity-graph-using-dbcontext.aspx^0|0|A|4|0|0|H|2|1|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@$E|U|F|V|1|W]]|A|$]]|$1|G|3|H|5|D|7|X|8|@]|9|@$E|Y|F|Z|1|10]]|A|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|A|$]]]|J|$K|$5|L|M|N|A|$O|P]]|Q|$5|L|M|N|A|$O|R]]]]

Google is your best friend here:

<ul>
<li>See <a href="https://en.wikipedia.org/wiki/Graph_database" rel="nofollow">this article</a> for general definition and explanation of graphs </li>
<li>See <a href="http://www.entityframeworktutorial.net/EntityFramework5/update-entity-graph-using-dbcontext.aspx" rel="nofollow">here</a> for specific information on EF and entity graphs</li>
</ul>

blocks|key|1089677|text|当实例化对象在关系中连接在一起时，它们被称为图或实体图。实体框架有一些关于如何维护图的重要规则。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1089678|例如，如果您有一个由具有角色的用户组成的用户(实体)图，则为“功能”。|1089679|当您分离用户时|unordered-list-item|1089680|用户将与此图断开连接，相关引用(图边)将被销毁。|1089681|您不能从用户迁移到角色/功能，因为图形边缘(关系)被破坏了。|1089682|我建议您购买“编程实体框架DbContext”一书(作者:EF)，您可以找到一个很好的解释：|1089683|http://shop.oreilly.com/product/0636920022237.do|offset|length|1089684|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|0|1C|0|0^^$0|@$1|2|3|4|5|6|7|X|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Z|8|@]|9|@]|A|$]]|$1|G|3|H|5|F|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|F|7|11|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|12|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|13|8|@]|9|@$O|14|P|15|1|16]]|A|$]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|N]]]]

When instantiated objects are joined together in a relationship they are referred to as
a graph, or an entity graph. The Entity Framework has some important rules about how
graphs are maintained.

Example, if you have a User(Entity) graph that consists of a User with Roles, Features.

<ul>
<li>When you detach the User</li>
<li>The User will be disconnected from this graph and the releationship references (Graph edges) will be destroyed.</li>
<li>You cannot travel from User to Roles/Features, because the graph edges (releationships) are destroyed.</li>
</ul>

I recommend you buy the "Programming Entity Framework DbContext" book (author: EF-Queen Julia Lerman) and you will find there a good explanation:

<a href="http://shop.oreilly.com/product/0636920022237.do" rel="nofollow noreferrer">http://shop.oreilly.com/product/0636920022237.do</a>

blocks|key|2127535|text|在Jpa中，hibernate获取具有关联的实体一直是性能问题。一次又一次地在事务中加载关联会导致n%2B1选择问题，并为了避免此类问题，使用了JPQL、联接、获取和标准api联接。但是，使用这两种方法获取数据也会导致交叉连接问题，这意味着所有表记录的交叉连接都会由hibernate返回到子程序中。另外，在实体级别上修改注释中定义的fetch变量对于某些情况也不是一个好的选择。因此，为了解决上述两个问题，引入了实体图。定义在实体图中的所有节点都是渴望获取的，而不管它们在实体级别上的定义如何。这些图作为查询的提示传递。通过将图形作为提示传递，交叉连接问题得到了解决，并且可以对获取行为进行运行时更改。关于代码，您可以查看我的github存储库：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2127536|https://github.com/vaneetkataria/Jpa-Hibernate/blob/master/jdbcToJpaMigration/src/test/java/com/katariasoft/technologies/jpaHibernate/entity/fetch/entitygraph/dynamic/MultiInstructorsDynamicEntityGrpahTests.java|offset|length|2127537|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|5V|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

In Jpa hibernate fetching entities with associtions has always been a question for performance. Lazily loading associations with in a transaction again and again results in n+1 select issues and to avoid such issues JPQL join fetch and Criteria api joins are used. But fetching data with these two also result in Cross join issues means Cross join of all table records are returned to apllication by hibernate. Also altering fetch variable defined in annotaions on entity level is also not a good option for some cases. Hence to solve the above two issues entity graphs has been intoduced. All nodes defined in entity graphs are always eager fetched irrespective of their definition on entity level. These graphs are passed as a hint to queries . By passing graphs as a hint Cross join issues are solved as well as run time alteration of fetch behaviour can take place. For code you can check my github repository :

<a href="https://github.com/vaneetkataria/Jpa-Hibernate/blob/master/jdbcToJpaMigration/src/test/java/com/katariasoft/technologies/jpaHibernate/entity/fetch/entitygraph/dynamic/MultiInstructorsDynamicEntityGrpahTests.java" rel="nofollow noreferrer">https://github.com/vaneetkataria/Jpa-Hibernate/blob/master/jdbcToJpaMigration/src/test/java/com/katariasoft/technologies/jpaHibernate/entity/fetch/entitygraph/dynamic/MultiInstructorsDynamicEntityGrpahTests.java</a>

I have been looking into some Entity framework tutorials and I have come across the word Entity Graph. I haven't got a clear idea about this term and its use. Can anyone provide info on this topic like what it is and its use in the context of entity framework?

What is entity graph in Entity Framework?

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

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

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

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

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

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

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

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

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

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

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我一直在研究一些实体框架教程，我遇到了单词实体图。我对这个词和它的用法不太清楚。有人能提供关于这个主题的信息，比如它是什么以及它在实体框架中的使用吗？

问实体框架中的实体图是什么？
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问实体框架中的实体图是什么？EN