使用nHibernate QueryOver加入子集

时间:2014-09-16 23:32:27

标签: c# sql nhibernate fluent-nhibernate

我正在使用nHibernate进行数据库访问。我需要做一个复杂的查询,以便在特定日期之后查找所有成员日记帐分录,并为每个成员设置特定值PreviousId。我可以轻松地为它编写SQL:

SELECT J.MemberId, J.PreviousId
FROM tblMemMemberStatusJournal J 
INNER JOIN (
    SELECT MemberId,
        MIN(EffectiveDate) AS EffectiveDate
    FROM tblMemMemberStatusJournal 
    WHERE EffectiveDate > @StartOfMonth
        AND (PreviousId is NOT null)
    GROUP BY MemberId
) AS X ON (X.EffectiveDate = J.EffectiveDate AND X.MemberId = J.MemberId)

但是我在尝试让nHibernate生成这些信息时遇到了很多麻烦。关于如何使用QueryOver,没有很多(任何)文档。

我一直在其他地方看到信息,但没有一个是非常明确的,并且很少有关于为什么事情以某种方式完成的实际解释。 Selecting on Sub Queries in NHibernate with Critieria API的答案没有给出足够的例子,因为我无法复制它。

我已经用这个创建了查询的内部部分:

IList<object[]> result = session.QueryOver<MemberStatusJournal>()
        .SelectList(list => list
            .SelectGroup(a => a.Member.ID)
            .SelectMin(a => a.EffectiveDate))
        .Where(j => (j.EffectiveDate > firstOfMonth) && (j.PreviousId != null))
        .List<object[]>();

根据分析器,这个SQL:

SELECT this_.MemberId           as y0_,
   min(this_.EffectiveDate) as y1_
FROM   tblMemMemberStatusJournal this_
WHERE  (this_.EffectiveDate > '2014-08-01T00:00:00' /* @p0 */
    and not (this_.PreviousLocalId is null))
GROUP  BY this_.MemberId

但我没有找到一个很好的例子,说明如何用父查询实际加入这个子集。有没有人有任何建议?

1 个答案:

答案 0 :(得分:1)

您实际上并未加入子集,而是对子集进行过滤。知道了这一点,您可以选择通过其他方式进行过滤,在本例中为相关子查询。

下面的解决方案首先创建一个detatched查询以充当内部子查询。我们可以通过使用别名将内部查询的属性与外部查询的属性相关联。

MemberStatusJournal memberStatusJournalAlias = null; // This will represent the 
                                                     // object of the outer query

var subQuery = QueryOver.Of<MemberStatusJournal>()
                  .Select(Projections.GroupProperty(Projections.Property<MemberStatusJournal>(m => m.Member.ID)))
                  .Where(j => (j.EffectiveDate > firstOfMonth) && (j.PreviousId != null))
                  .Where(Restrictions.EqProperty(
                             Projections.Min<MemberStatusJournal>(j => j.EffectiveDate),
                             Projections.Property(() => memberStatusJournalAlias.EffectiveDate)
                         )
                        )
                  .Where(Restrictions.EqProperty(
                            Projections.GroupProperty(Projections.Property<MemberStatusJournal>(m => m.Member.Id)),
                            Projections.Property(() => memberStatusJournalAlias.Member.Id)
                       ));

var results = session.QueryOver<MemberStatusJournal>(() => memberStatusJournalAlias)
                     .WithSubquery
                     .WhereExists(subQuery)
                     .List();

这将产生如下的SQL查询:

SELECT blah
FROM tblMemMemberStatusJournal J 
WHERE EXISTS (
    SELECT J2.MemberId
     FROM tblMemberStatusJournal J2
    WHERE J2.EffectiveDate > @StartOfMonth
        AND (J2.PreviousId is NOT null)
    GROUP BY J2.MemberId
    HAVING MIN(J2.EffectiveDate) = J.EffectiveDate
    AND J2.MemberId = J.MemberId
)

这看起来效率低于您打开问题的inner join查询。但我的经验是SQL查询优化器足够聪明,可以将其转换为内部联接。如果要确认这一点,可以使用SQL Studio生成并比较两个查询的执行计划。