Lambda expressions and expression trees can be used to build dynamic queries at runtime. This is especially valuable when you want to construct complex queries based on user input or when dealing with dynamic data sources.
Here's an example:
using System;
using System.Collections.Generic;
using System.Linq;
using System.Linq.Expressions;
public class Person
{
public string Name { get; set; }
public int Age { get; set; }
}
public class Program
{
public static void Main()
{
var people = new List<Person>
{
new Person { Name = "Alice", Age = 30 },
new Person { Name = "Bob", Age = 25 },
new Person { Name = "Charlie", Age = 35 },
};
// Create a dynamic query based on user input
Expression<Func<Person, bool>> dynamicQuery = CreateDynamicQuery("Age", 30);
// Apply the dynamic query to filter the data
var filteredPeople = people.AsQueryable().Where(dynamicQuery);
foreach (var person in filteredPeople)
{
Console.WriteLine($"{person.Name}, Age: {person.Age}");
}
}
public static Expression<Func<Person, bool>> CreateDynamicQuery(string propertyName, int value)
{
var parameter = Expression.Parameter(typeof(Person), "p");
var property = Expression.Property(parameter, propertyName);
var constant = Expression.Constant(value);
var body = Expression.GreaterThanOrEqual(property, constant);
return Expression.Lambda<Func<Person, bool>>(body, parameter);
}
}
In this example:
We define a
Personclass to represent individuals with aNameandAge.We create a dynamic query using a
CreateDynamicQuerymethod that takes a property name and a value. This method builds an expression tree dynamically to represent the query condition (Age >= 30in this case).We use the dynamic query with
Whereto filter the list of people based on the user-defined criteria.
This approach allows you to construct queries dynamically based on user input or other runtime conditions, making your code more flexible and adaptable to various data filtering requirements. It's especially useful when building data-driven applications or systems where query criteria are not known at compile time.
Top comments (1)
This approach may lead to performance issues : the internal cache of EF core will grow for every values of 'age' because the corresponding expression is a constant. So any different value will generate a new query efcore should compile and save in the cache.
The problem is the same with your database engine (at least with SQL server) : a constant value will be translated in ... A constant value in SQL. The correct version of the SQL querry should probably be parameterezid, so the compiled version of the query is put in cache one time.