Introduction
This Article discusses the basic differences between IEnumerable and IQueryable Interface. The article is for Beginners who are eager to know about these differences, this article is also for newbies or novice who are in the learning stage.
Background
In LINQ to query data from database and collections, we use IEnumerable
and IQueryable for data manipulation. IEnumerable is inherited by
IQueryable, hence it has all the features of it and except this, it has
its own features. Both have their own importance to query data and data
manipulation. Let’s see both the features and take the advantage of both
the features to boost your LINQ Query performance.
IEnumerable
- IEnumerable exists in System.Collections Namespace.
- IEnumerable can move forward only over a collection, it can’t move backward and between the items.
- IEnumerable is best to query data from in-memory collections like List, Array etc.
- While
query data from database, IEnumerable execute select query on server
side, load data in-memory on client side and then filter data.
- IEnumerable is suitable for LINQ to Object and LINQ to XML queries.
- IEnumerable supports deferred execution.
- IEnumerable doesn’t supports custom query.
- IEnumerable doesn’t support lazy loading. Hence not suitable for paging like scenarios.
- Extension methods supports by IEnumerable takes functional objects.
IEnumerable Example
MyDataContext dc = new MyDataContext ();
IEnumerable<Employee> list = dc.Employees.Where(p => p.Name.StartsWith("S"));
list = list.Take<Employee>(10);
Generated SQL statements of above query will be :
SELECT [t0].[EmpID], [t0].[EmpName], [t0].[Salary] FROM [Employee] AS [t0]
WHERE [t0].[EmpName] LIKE @p0
*Notice that in this query
"top 10" is missing since IEnumerable filters records on client side.
IQueryable
- IQueryable exists in System.Linq Namespace.
- IQueryable can move forward only over a collection, it can’t move backward and between the items.
- IQueryable is best to query data from out-memory (like remote database, service) collections.
- While query data from database, IQueryable execute select query on server side with all filters.
- IQueryable is suitable for LINQ to SQL queries.
- IQueryable supports deferred execution.
- IQueryable supports custom query using CreateQuery and Execute methods.
- IQueryable support lazy loading. Hence it is suitable for paging like scenarios.
- Extension methods supports by IEnumerable takes expression objects means expression tree.
IQueryable Example
MyDataContext dc = new MyDataContext ();
IQueryable<Employee> list = dc.Employees.Where(p => p.Name.StartsWith("S"));
list = list.Take<Employee>(10);
*Notice that in this query
"top 10" is existing since IQueryable executes query in SQL server with all filters.
Generated SQL statements of above query will be :
SELECT TOP 10 [t0].[EmpID], [t0].[EmpName], [t0].[Salary] FROM [Employee] AS [t0]
WHERE [t0].[EmpName] LIKE @p0
Points of Interest
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.
If some of you are really interested in knowing these differences you can also refer to the MSDN
A .Net Developer with a varied interest in programming using Web and Desktop application using ASP.Net, C#, AJAX, WCF, WPF, Silverlight,SQL Server 2008 R2 and Fluent NHibernate. A quick learner and a badminton enthusiast.
In my spare time i try to learn some new technologies and explore what others are doing.