NHibernate 标准 fetchmode

发布于 2024-09-28 06:44:17 字数 662 浏览 1 评论 0原文

我有一个类型 Type1，其属性 Type2s 由 List 组成。我已为该属性配置了 NHibernate 映射，如下所示：

[Map(0, Table = "Type2s", Schema = "MySchema", Cascade = CascadeStyle.All, Lazy = true, Inverse = true)]
[Key(1, Column = "Type1Id")]
[OneToMany(2, Class = "Type2, MyNamespace")]

这两个用于检索 Type1 实例的条件之间的行为有什么区别：

var criteria1 = DetachedCriteria.For<MyType1>();

var criteria2 = DetachedCriteria.For<MyType1>().SetFetchMode("Type2s", FetchMode.Join);

当我从这些条件的可执行条件上调用 .List 时，大概是检索与关联的 Type2 的 SQL每个 Type1 实例在我实际尝试访问该属性之前不会运行，因为该属性被标记为惰性。这是一个正确的假设吗？

如果我想强制评估 Lazy 属性，如何最好地实现这一点？

原文

I have a type Type1 with a property Type2s consisting of a List<Type2>. I have configured the NHibernate mapping for the property as follows:

[Map(0, Table = "Type2s", Schema = "MySchema", Cascade = CascadeStyle.All, Lazy = true, Inverse = true)]
[Key(1, Column = "Type1Id")]
[OneToMany(2, Class = "Type2, MyNamespace")]

What is the difference in behavior between these two criteria for retrieval of Type1 instances:

var criteria1 = DetachedCriteria.For<MyType1>();

var criteria2 = DetachedCriteria.For<MyType1>().SetFetchMode("Type2s", FetchMode.Join);

When I invoke .List on the executable criteria from these criteria, presumably the SQL to retrieve the Type2s associated with each Type1 instance is not run until I actually attempt to access the property because the property is marked as being Lazy. Is this a correct assumption?

If I want to force evaluation of the Lazy property how can this best be achieved?

分享到QQ

分享到微博