This post explains how to extend the Dynamic Linq library to support the "Contains" extension method. This post also can serve as a base for further extension of the Dynamic Linq Library and adding support to more extension methods.
Linq is an amazing programming model, brought to life by the Microsoft.NET Framework 3.5, that introduces data queries as a first-class concept into any Microsoft programming langage.
Linq allows you to build strongly type queries to access data in any source for which a Linq support library is available, including MS SQL, data objects (through IEnumerable and IQueryable), Entity Framework and more.
Even though the regular, strongly typed approach to building queries is definitively recommended, in some cases arises the need for dynamically building queries. For this purpose Microsoft freely provides an open source dynamic Linq query library. Cases for using dynamic queries could be for example: you might want to provide business intelligence UI within your application that allows an end-user business analyst to use drop-downs to build and express their own custom queries/views on top of data. Another example is the creation of RESTfull service interfaces that accept query string parameters that could be converted to dynamic linq queries.
Please refer the the Scott Guthrie post for more information on the Dynamic Linq Query library:
I found this library very usefull and used it in several scenarios. However this library does not support all of the Linq extensions. I had the need for building dynamic queries with the "Contains" extension which was not supported by the Microsoft Dynamic Linq library. This post explains how to extend the Dynamic Linq library to support the "Contains" extension method.
Sample Code
Here is the sample application we use to illustrate our tallks (You can download the source code here) :
We define a class "Contact". For the purpose of demonstration, we do not connect to a data source, but have a static "GetContactList" method that return a collection of users.
1 public class Contact 2 { 3 public string FirstName { get; set; } 4 public string LastName { get; set; } 5 public DateTime BirthDate { get; set; } 6 public string Country { get; set; } 7 8 public Contact(string firstName, string lastName, DateTime birthDate, string country) 9 { 10 FirstName = firstName; 11 LastName = lastName; 12 BirthDate = birthDate; 13 Country = country; 14 } 15 16 public override string ToString() 17 { 18 return string.Concat(FirstName, " ", LastName, " ", BirthDate, " ",Country); 19 } 20 21 public static List‹contact› GetContactsList() 22 { 23 var result = new List‹contact›(); 24 25 result.Add(new Contact("Zephr", "Austin", new DateTime(1967, 11, 07), "Afghan")); 26 result.Add(new Contact("Odette", "Bean", new DateTime(1993, 05, 18), "Uzbekistan")); 27 result.Add(new Contact("Maggie", "Mcson", new DateTime(2001, 06, 12),"Kiribati")); 28 ... 29 ... 30 31 return result; 32 } 33 }
The Case – Use of the Dynamic Linq Library and missing support for the “Contains” extension method
Let's take a first example of simple Linq query to get the contacts located in Austria. Using regular Linq, you write the following query:
var query = from c in Contact.GetContactsList() where c.Country == "Austria" select c;
Or the equivalent query, using extension methods and lambda
var query = Contact.GetContactsList().Where(c => c.Country == "Austria");
We will keep the second syntax as the dynamic linq library does not support the first syntax.
We can then iterate the query result and retrieve relevant contact information:
foreach (var contact in query) { Console.WriteLine(contact.ToString()); }
Doing the same query using dynamic Linq:
query = Contact.GetContactsList().AsQueryable().Where("Country == @0", "Austria");
Please not the extra "AsQueryable()" call because the dynamic extension applies on collections implementing IQueryable. Then Iterating the results is just the same as with regular Linq.
The Dynamic Linq library also supports more complex queries. For instance here is the Dynamic Linq query to retrieve all contacts in Austria, born in 1957:
query = Contact.GetContactsList().AsQueryable().Where("Country == @0 && BirthDate.Year == 1957", "Austria");
Everythings seems to magically work so far. Let’s try now a more complex scenario: when want to retrieve the list of contacts located in given list of countries. Let’s say : all contacts located in either Austria or Poland. For such a purpose, a common solution is to use the “Contains” extension method:
query = Contact.GetContactsList().Where(c => new List<string>>() { "Austria","Poland" }.Contains(c.Country));
In Linq to SQL, the result pseudo SQL projection would be:
select * from contact c where c.Country in (‘Austria’, ‘Poland’);
Let’s try to write the same query in Dynamic Linq (using parameters to pass the input list of countries):
query = Contact.GetContactsList().AsQueryable().Where("@0.Contains(Country)", newList<string>() { "Austria", "Poland" });
This result at runtime to the following exception: “No applicable aggregate method 'Contains' exists”,
Emphasizing the fact the Dynamic Linq library does not have support for the “Contains” extension method. The following section will explains how to add support for “Contains”.
Add support for the “Contains” extension method
Analyzing the “Dynamic.cs” class that adds support for Dynamic Linq, you’ll find the definition of the IEnumerableSignatures interface. This interface lists all IEnumerable extension methods that are supported by the Dynamic Linq library. You should add the “Contains” extension method signature:
interface IEnumerableSignatures { void Contains(object selector); void Where(bool predicate); void Any(); void Any(bool predicate); void All(bool predicate); void Count(); void Count(bool predicate); void Min(object selector); void Max(object selector); void Sum(int selector); void Sum(int? selector); void Sum(long selector); void Sum(long? selector); void Sum(float selector); void Sum(float? selector); void Sum(double selector); void Sum(double? selector); void Sum(decimal selector); void Sum(decimal? selector); void Average(int selector); void Average(int? selector); void Average(long selector); void Average(long? selector); void Average(float selector); void Average(float? selector); void Average(double selector); void Average(double? selector); void Average(decimal selector); void Average(decimal? selector); }
The IEnumerableSignatures interface is then used in the following method:
Expression ParseAggregate(Expression instance, Type elementType, string methodName, int errorPos) { ParameterExpression outerIt = it; ParameterExpression innerIt = Expression.Parameter(elementType, ""); it = innerIt; Expression[] args = ParseArgumentList(); it = outerIt; MethodBase signature; if (FindMethod(typeof(IEnumerableSignatures), methodName, false, args, out signature) != 1) throw ParseError(errorPos, Res.NoApplicableAggregate, methodName); Type[] typeArgs; if (signature.Name == "Min" || signature.Name == "Max") { typeArgs = new Type[] { elementType, args[0].Type }; } else { typeArgs = new Type[] { elementType }; } if (args.Length == 0) { args = new Expression[] { instance }; } else { args = new Expression[] { instance, Expression.Lambda(args[0], innerIt) }; } return Expression.Call(typeof(Enumerable), signature.Name, typeArgs, args); }
There 2 changes to perform to that method.
Fist, the arguments are constructed using the following line:
args = new Expression[] { instance, Expression.Lambda(args[0], innerIt) };
this has to be changed specifically for the Contains methods to the following:
args = new Expression[] { instance, args[0] };
Reason is that the signature of the Contains extension methods differs from the others. Let’s take an example: here are the definitions for the “Any” and “Contains” extension methods of the IEnumerable<> interface (classe “System.Linq.Enumerable”):
Any<TSource>(this.System.Collections.Generic.IEnumerable<TSource>, System.Func<TSource,bool>); Contains<TSource>(this.System.Collections.Generic.IEnumerable<TSource>, TSource);
You can see that the parameter of the “Any” extension method is a lambda expression taking “TSource” (type of innerIt in our Dynamic Linq library) as entry and returning ”bool” .This explains the transformation Expression.Lambda(args[0], innerIt). In the case of the “Contains” extension method, type of the argument is not a Lambda but just “TSource”.
Next change is the following: the Dynamic Linq library transforms the input string to a proper Linq query by parsing the input string. It internally keeps a context to the current collection being processed. This is the use of the field “innerIt”. When processing our list of “Contacts”, the innerIt represent a “Contact”. However, when processing the “Contains” method, the context changes from the list of “Contacts” to the list being the source for the “Contains” method; in our case: the list of string representing country name. Therefore the parsing of the following dynamic Linq expression:
query = Contact.GetContactsList().AsQueryable().Where("@0.Contains(Country)", newList<String>() { "Austria", "Poland" });
will not work: the parser will try to find a property “Country” on type String, where we meant a property “Country” on “Contact”.
In fact the previous query is equivalent to:
query = Contact.GetContactsList().AsQueryable().Where("@0.Contains(it.Country)", newList<String>() { "Austria", "Poland" });
Where “it” is the keyword defined in the Dynamic Linq library to represent the current element. It represents here the current item in the list {“Austria”, “Poland”}. What we would like here is the following syntax:
query = Contact.GetContactsList().AsQueryable().Where("@0.Contains(outerIt.Country)", newList<String>() { "Austria", "Poland" });
where “outerIt” represents the englobing context: the list of “Contacts”. For this we should define an “outerIt” keyword, and use it in the “ParseAggregate” method. The new implementation of the “ParseAggregate” methods is now:
Expression ParseAggregate(Expression instance, Type elementType, string methodName, int errorPos) { outerIt = it; ParameterExpression innerIt = Expression.Parameter(elementType, ""); it = innerIt; Expression[] args = ParseArgumentList(); it = outerIt; MethodBase signature; if (FindMethod(typeof(IEnumerableSignatures), methodName, false, args, out signature) != 1) throw ParseError(errorPos, Res.NoApplicableAggregate, methodName); Type[] typeArgs; if (signature.Name == "Min" || signature.Name == "Max") { typeArgs = new Type[] { elementType, args[0].Type }; } else { typeArgs = new Type[] { elementType }; } if (args.Length == 0) { args = new Expression[] { instance }; } else { if (signature.Name == "Contains") args = new Expression[] { instance, args[0] }; else args = new Expression[] { instance, Expression.Lambda(args[0], innerIt) }; } return Expression.Call(typeof(Enumerable), signature.Name, typeArgs, args); }
By the way: it is important to mention that since “it” and “outerIt” are defined keywords, they become reserved keywords and should not be used as properties or method definitions in your data classes, if you intend to access them as part of dynamic queries. It would result in a runtime error. Since the common used code standards are to use only capitalized names for public properties and methods, it should be alright in most of the cases.
Remains the use of the “outerIt” keyword. Definition of the keyword and class level storage of its current value:
static readonly string keywordOuterIt = "outerIt"; ParameterExpression outerIt;
Taking into account the new keyword in « ParseIdentifier »
Expression ParseIdentifier() { ValidateToken(TokenId.Identifier); object value; if (keywords.TryGetValue(token.text, out value)) { if (value is Type) return ParseTypeAccess((Type)value); if (value == (object)keywordIt) return ParseIt(); if (value == (object)keywordOuterIt) return ParseOuterIt(); if (value == (object)keywordIif) return ParseIif(); if (value == (object)keywordNew) return ParseNew(); NextToken(); return (Expression)value; } ... ...
And new method “ParseOuterIt”:
Expression ParseOuterIt() { if (outerIt == null) throw ParseError(Res.NoItInScope); NextToken(); return outerIt; }
Conclusion
That’s it ! The Dynamic Linq library is now supporting the « Contains » extension method
You’ll find the modified “Dynamic.cs” class as part of the code sample. You can now write and successfully run queries likes the following:
query = Contact.GetContactsList().AsQueryable().Where("@0.Contains(outerIt.Country)", newList<String>() { "Austria", "Poland" });
or:
query = Contact.GetContactsList().AsQueryable().Where("@0.Contains(outerIt.Country) && it.BirthDate.Year > @1", new List<string>() { "Austria", "Poland" }, 1955);
This post can be used to further extend the Dynamic Linq library and add support for more extension methods.
Hope this can help other who faced the same limitation and help move forward the Dynamic Linq Library!
You can download the source code for the sample project here. or here