LINQ to Entities和LINQ to Objects如何处理强制转换的区别

时间:2014-12-22 15:31:31

标签: c# linq entity-framework linq-to-entities

我最近加入了一个项目,其中Sort方法有条件地将lambda表达式传递给LINQ查询以定义应该对哪个属性进行排序。问题是lambda表达式是在Func<TEntity, Object&gt;中传递的。而不是在Expression<Func<TEntity, Object>>中,因此排序发生在内存而不是数据库中(因为OrderBy的重载被调用了IEnumerable。这是SortWithDelegate中的版本(见下文)。

当我使用Expression<Func<TEntity, Object>>(参见下面的SortWithExpression)时,当在orderBy参数中传递字符串属性时,在数据库中正确完成排序。但是,当我尝试使用Expression<Func<TEntity, Object>>对整数(或日期时间)进行排序时,我收到以下错误:

Unable to cast the type 'System.Int32' to type 'System.Object'. LINQ to Entities only supports casting EDM primitive or enumeration types.

为了避免这种情况,我必须将整数或日期时间字段包装在匿名类型内,如下所示:orderByFunc = sl => new {sl.ParentUnit.Id};。我知道我需要这样做,因为Func的返回类型是Object。但是,我不明白为什么在使用LINQ to Entities提供程序而不是LINQ to Objects提供程序时需要这样做?

void Main()
{
    var _context = new MyContext();

    string sortProperty = "Id";
    bool sortAscending = false;


    IQueryable<Qualification> qualifications = _context.Qualifications.Include(q => q.ParentUnit);

    qualifications = SortWithExpression(sortProperty, sortAscending, qualifications);

    qualifications.Dump();

}

private static IQueryable<Qualification> SortWithDelegate(string orderBy, bool sortAscending, IQueryable<Qualification> qualificationsQuery)
{
    Func<Qualification, Object> orderByFunc;

    switch (orderBy)
    {
        case "Name":
            orderByFunc = sl => sl.Name;
            break;
        case "ParentUnit":
            orderByFunc = sl => sl.ParentUnit.Name;
            break;
        case "Id":
            orderByFunc = sl => sl.ParentUnit.Id;
            break;
        case "Created":
            orderByFunc = sl => sl.Created;
            break;
        default:
            orderByFunc = sl => sl.Name;
            break;
    }

    qualificationsQuery = sortAscending
        ? qualificationsQuery.OrderBy(orderByFunc).AsQueryable()
            : qualificationsQuery.OrderByDescending(orderByFunc).AsQueryable();

    return qualificationsQuery;
}

private static IQueryable<Qualification> SortWithExpression(string orderBy, bool sortAscending, IQueryable<Qualification> qualificationsQuery)
{
    Expression<Func<Qualification, Object>> orderByFunc;

    switch (orderBy)
    {
        case "Name":
            orderByFunc = sl => sl.Name;
            break;
        case "ParentUnit":
            orderByFunc = sl => sl.ParentUnit.Name;
            break;
        case "Id":
            orderByFunc = sl => new {sl.ParentUnit.Id};
            break;
        case "Created":
            orderByFunc = sl => new {sl.Created};
            break;
        default:
            orderByFunc = sl => sl.Name;
            break;
    }

    qualificationsQuery = sortAscending
        ? qualificationsQuery.OrderBy(orderByFunc)
            : qualificationsQuery.OrderByDescending(orderByFunc);

    return qualificationsQuery;
}

以为我会为这个问题添加自己的解决方案。为了避免装箱intdatetime,我在IQueryable<T>上创建了一个通用扩展方法,我在其中传递lambda表达式以指示排序字段和一个布尔值,指示排序顺序是否应该是否提升:

    public static IQueryable<TSource> OrderBy<TSource, TResult>(this IQueryable<TSource> query, Expression<Func<TSource, TResult>> func, bool sortAscending)
    {
        return sortAscending ?
            query.OrderBy(func) :
                query.OrderByDescending(func);
    }

    private static IQueryable<Qualification> Sort(string orderBy, bool sortAscending, IQueryable<Qualification> qualificationsQuery)
    {
        switch (orderBy)
        {
            case "Name":
                return qualificationsQuery.OrderBy(sl => sl.Name, sortAscending);
            case "ParentUnit":
                return qualificationsQuery.OrderBy(s1 => s1.ParentUnit.Name, sortAscending);
            default:
                return qualificationsQuery.OrderBy(sl => sl.Name, sortAscending);
        }
    }

1 个答案:

答案 0 :(得分:1)

表达式树的名字暗示着关于做某事的表达。你可以访问表达式并将它们解释为你自己的业务,或者像lambda表达式一样,你可以编译它们并作为委托调用。

当您将表达式传递给Linq to Entities中的orderby方法时,Linq将访问实体,在您的情况下,&#34; Int32 to Object&#34;将生成异常,因为它被解释为成为数据库查询的列名的MemberInfo。但是当你将它用作Func委托时,它无法被翻译,并且它将作为委托调用,用于orderby方法的排序算法。