CODEWITHSUNDEEP
asp.net-mvcentity-frameworksearchrepository
Seen
Seen

Reputation: 4194

Multiple search criteria in a repository

I have a question for how to implement multiple criteria for a repository pattern in ASP.net MVC. Imagine a POCO class in EF4

public class people
{ String Name {get;set;}
float Height {get;set;}
float Weight {get;set;}
int age {get;set;}
....
}

If I build up a repository as IPeopleRepository, what kind of methods should I implement for a multiple criteria search (e.g Age > 30, Height >80). Those criteria would be related to the properties in the class and some of the input could be null. Of course I can write a method like 

People SearchPeople (int age, float height.....)

but I have to judge if every variable would be null and append onto the search queries..

So do you have any good ideas on how to implement this function in EF?

Upvotes: 4

Views: 5341

Answers (3)

Tien Do
Tien Do

Reputation: 11079

Basically I think there are three options:

  1. Use Specification pattern and create as many single specification as you need then you can more complex specification by combining them via And/Or/Not operators. You can look at here for an example http://code.google.com/p/linq-specifications/

  2. Create a search method that accept an input predicate, it's most simple one since it leaves all criteria filtering works to consumers.

  3. Create a search method with different criteria, then build dynamic Linq expression. There is a PredicateBuilder here: http://www.linqpad.net (look for LinqKit project).

Upvotes: 1

RPM1984
RPM1984

Reputation: 73123

It sounds like your looking for something like the Specification pattern.

There is a great article involving EF4 / POCO / Repository / Specification pattern here.

Although i like the pattern, i find it a bit overkill in simple scenarios.

I ended up using the "pipes and filters" technique - basically IQueryable<T> extension methods on your objects to make your repository code fluent.

For a search criteria however, i would be tempted to allow the consuming code to supply the predicate, then you don't have to worry about the parameters.

So the definition would be like this:

public People SearchPeople(Expression<Func<People,bool>> predicate)
{
   return _context.People.SingleOrDefault(predicate);
}

Then the code simply supplies the predicate.

var person = _repository.SearchPeople(p => p.Age > 30 && p.Height > 80);

Some people don't like this technique, as it gives too much "power" to the consumer, because they might supply a predicate like p.Id > 0 and return all the rows in the database.

To counteract that, provide an optional parameter for maxRows. If it's not supplied, default to 100 rows.

Upvotes: 8

Alex Aza
Alex Aza

Reputation: 78487

First, you need to think if you really need repository search method.
You might want to do direct queries instead of wrapping them to repository.

However, if you think you need the search method than you will likely use something like this:

private People SearchPeople(int? age, float? height)
{
    var baseQuery = db.People;

    if (age != null)
        baseQuery = baseQuery.Where(arg => arg.Age > age);
    if (height != null)
        baseQuery = baseQuery.Where(arg => arg.Height > height);

    return baseQuery.ToList();
}

Although you didn't want to do this, I can't think of better solution.

Upvotes: 4

Related Questions