IEnumerable<T>
represents a forward-only cursor of T
. .NET 3.5 added extension methods that included the LINQ standard query operators
like Where
and First
, with any operators that require predicates or anonymous functions taking Func<T>
.
IQueryable<T>
implements the same LINQ standard query operators, but accepts Expression<Func<T>>
for predicates and anonymous functions. Expression<T>
is a compiled expression tree, a broken-up version of the method ("half-compiled" if you will) that can be parsed by the queryable's provider and used accordingly.
For example:
IEnumerable<Person> people = GetEnumerablePeople();
Person person = people.Where(x => x.Age > 18).FirstOrDefault();
IQueryable<Person> people = GetQueryablePeople();
Person person = people.Where(x => x.Age > 18).FirstOrDefault();
In the first block, x => x.Age > 18
is an anonymous method (Func<Person, bool>
), which can be executed like any other method. Enumerable.Where
will execute the method once for each person, yield
ing values for which the method returned true
.
In the second block, x => x.Age > 18
is an expression tree (Expression<Func<Person, bool>>
), which can be thought of as "is the 'Age' property > 18".
This allows things like LINQ-to-SQL to exist because they can parse the expression tree and convert it into equivalent SQL. And because the provider doesn't need to execute until the IQueryable
is enumerated (it implements IEnumerable<T>
, after all), it can combine multiple query operators (in the above example Where
and FirstOrDefault
) to make smarter choices on how to execute the entire query against the underlying data source (like using SELECT TOP 1
in SQL).
See:
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…