Dynamic where condition in LINQ
Solution 1
So, if flag
is false
you need all Jhoms, and if flag
is true you need only the Jhoms in the IT department
This condition
!flag || (e.Field<string>("EmployeeDepartment") == "IT"
satisfies that criterion (it's always true if flag is false, etc..), so the query will become:
from e in employee
where e.Field<string>("EmployeeName") == "Jhom"
&& (!flag || (e.Field<string>("EmployeeDepartment") == "IT")
select e.Field<string>("EmployeeID")
also, this e.Field<string>("EmployeeID")
business, smells like softcoding, might take a look into that. I guess
from e in employee
where e.EmployeeName == "Jhom"
&& (!flag || (e.EmployeeDepartment == "IT")
select e.EmployeeID
would be more compact and less prone to typing errors.
EDIT: This answer works for this particular scenario. If you have lots of this kinds of queries, by all means investingate the patterns proposed in the other answers.
Solution 2
Please check out the full blog post: Dynamic query with Linq
There are two options you can use:
string condition = string.Empty;
if (!string.IsNullOrEmpty(txtName.Text))
condition = string.Format("Name.StartsWith(\"{0}\")", txtName.Text);
EmployeeDataContext edb = new EmployeeDataContext();
if(condition != string.empty)
{
var emp = edb.Employees.Where(condition);
///do the task you wnat
}
else
{
//do the task you want
}
Predicate builder works similar to Dynamic LINQ library but it is type safe:
var predicate = PredicateBuilder.True<Employee>();
if(!string.IsNullOrEmpty(txtAddress.Text))
predicate = predicate.And(e1 => e1.Address.Contains(txtAddress.Text));
EmployeeDataContext edb= new EmployeeDataContext();
var emp = edb.Employees.Where(predicate);
difference between above library:
- PredicateBuilder allows to build typesafe dynamic queries.
- Dynamic LINQ library allows to build queries with dynamic Where and OrderBy clauses specified using strings.
Solution 3
You can chain methods :
public void test(bool flag)
{
var res = employee.Where( x => x.EmployeeName = "Jhom" );
if (flag)
{
res = res.Where( x => x.EmployeeDepartment == "IT")
}
var id = res.Select(x => x.EmployeeID );
}
Related videos on Youtube
Shivi
Updated on October 11, 2020Comments
-
Shivi over 3 years
I have a scenario where I have to use a dynamic where condition in LINQ.
I want something like this:
public void test(bool flag) { from e in employee where e.Field<string>("EmployeeName") == "Jhom" If (flag == true) { e.Field<string>("EmployeeDepartment") == "IT" } select e.Field<string>("EmployeeID") }
I know we can't use the 'If' in the middle of the Linq query but what is the solution for this?
Please help...
-
markdorison about 13 yearsI don't understand why the downvote ? Maybe an explanation could help me improve my answer ?
-
Dan Abramov about 13 yearsFirst example seems to be taken off the context. What's the point of checking
condition
for emptiness if it has just been assignedstring.Empty
? I'll correct this now.. -
Pranay Rana about 13 years@gaearon - if there are more no of condition thats y i put there ...i alreay posted link of full post where you can see detail
-
Dan Abramov about 13 yearsI believe this is not what is being asked. The issue is not unknown property name but unknown (may I call it so) ‘chainity’. Your answer does not reflect how exactly you can chain queries with Dynamic LINQ. More to that, your example is wrong because
EmployeeName
is notEmployee
's property, it is a string passed toField
method. -
Dan Abramov about 13 yearsAnd, last but probably main reason for downvote, is my subjective opinion that this is a bad idea. The question does not call for Dynamic LINQ, all that is needed is arbitrary chaining, which is already possible using explicit LINQ method calls. Dynamic and not typesafe code must only be introduced where it's hard to achieve the same with type safety (e.g. user entering complicated expression right in search box). Dynamic LINQ is better than parsing but much worse than typesafe query which is very possible and even desirable with this question.
-
Kai Hartmann over 7 yearsThis is the most straight forward.