IEnumerable Vs IQueryable

Many developers gets confused between IEnumerable and IQueryable. When it comes to writing code, both looks very similar. However there are many difference between them which needs to be taken care of while writing code. Both have some intended usability scenarios for which they are made.

Below lists the differences between them based on their properties :

	IEnumerable	IQueryable
Namespace	System.Collections Namespace	System.Linq Namespace
Derives from	No base interface	Derives from IEnumerable
Deferred Execution	Supported	Supported
Lazy Loading	Not Supported	Supported
How does it work	While querying data from database, IEnumerable execute select query on server side, load data in-memory on client side and then filter data. Hence does more work and becomes slow.	While querying data from database, IQueryable execute select query on server side with all filters. Hence does less work and becomes fast.
Suitable for	LINQ to Object and LINQ to XML queries.	LINQ to SQL queries.
Custom Query	Doesn’t supports.	Supports using CreateQuery and Execute methods.
Extension mehtod parameter	Extension methods supported in IEnumerable takes functional objects.	Extension methods supported in IEnumerable takes expression objects i.e. expression tree.
When to use	when querying data from in-memory collections like List, Array etc.	when querying data from out-memory (like remote database, service) collections.
Best Uses	In-memory traversal	Paging

Comments

C# Generic Factory

Implement Factory pattern using generics public interface IDoWork { string DoWork(); } Declare an Interface first by abstracting the common functionality Here I am taking the example of DoWork public class Manager : IDoWork { public string DoWork() { return "Manager Manages School" ; } } Implement the IDoWork in concrete classes as shown public class Teacher : IDoWork { public string DoWork() { return "Teacher teaches student in school" ; ...

How to enable windows authentication in PostgreSQL

1. Steps to create user or role in PostgreSQL · Open pgAdmin III · Login to PostgreSQL database · Select “Login Roles” and right click on mouse to view the context menu · Select “New Login Role” from context menu · Enter desired user name in “Role name” text box · Select “Definition” tab in “New Login Role” window · Enter desired Password in the given text box · Select “Role privileges” tab in “New Login Role” window · Select the privileges for the entered user or role · Select “SQL”...

UML - Association, Aggregation, Composition, Generalization, Specialization, Realization and Dependency

Association Association is a simple relationship between two classes. For example A relationship between Professor Class and Student class is known as Association. Both Classes can exist without each other, so Professor and Student are two independent classes. In this kind of relationships there will not be any owner class. Both classes have their own life cycle. UML Notation: Aggregation Aggregation is a special type of Association. It is known as “Has-A” relationship. For example A Department class can contain Professor Class. Here Department class is owner class. Here in this relationship even after deleting Department class, Professor Class can exits. UML Notation: Composition Composition is a special type of Aggregation. It is known as “Is-A” relationship. For example A University Class has many Department class. Here University and Department objects are dependent on each other. If we delete Univ...

Prime Instance

Search This Blog